View M29DW128F70ZA6_4928511.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

preliminary data this is preliminary information on a new product now in development or undergoing evaluation. details are subject to change without notice. rev 1.0 august 2005 1/93 1 m29dw128f 128 mbit (16mb x8 or 8mb x16, multiple bank, page, boot block) 3v supply, flash memory features summary supply voltage ?v cc = 2.7v to 3.6v for program, erase and read ?v ccq = 1.65v to 3.6v for input/output ?v pp =12v for fast program (optional) asynchronous random/page read ? page width: 8 words ? page access: 25, 30ns ? random access: 60, 70ns programming time ? 10s per byte/word typical ? 4 words / 8 bytes program ? 32-word write buffer erase verify memory blocks ? quadruple bank memory array: 16mbit+48mbit+48mbit+16mbit ? parameter blocks (at top and bottom) dual operations ? while program or erase in one bank, read in any of the other banks program/ erase suspend and resume modes ? read from any block during program suspend ? read and program another block during erase suspend unlock bypass program ? faster production/batch programming common flash interface ? 64 bit security code 100,000 program/erase cycles per block low power consumption ? standby and automatic standby hardware block protection ?v pp /wp pin for fast program and write protect of the four outermost parameter blocks security features ? standard protection ? password protection extended memory block ? extra block used as security block or to store additional information electronic signature ? manufacturer code: 0020h ? device code: 227eh + 2220h + 2200h ecopack ? packages available bga tsop56 (nf) 14 x 20mm tbga64 (za) 10 x 13mm www.st.com
m29dw128f 2/93 contents 1 summary description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.1 address inputs (a0-a22) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2 data inputs/outputs (dq0-dq7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3 data inputs/outputs (dq8-dq14) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.4 data input/output or address input (dq15a?1) . . . . . . . . . . . . . . . . . . . . . . 14 2.5 chip enable (e) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.6 output enable (g) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.7 write enable (w) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.8 v pp/ write protect (v pp/ wp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.9 reset/block temporary unprotect (rp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.10 ready/busy output (rb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.11 byte/word organization select (byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.12 v ccq supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.13 v cc supply voltage (2.7v to 3.6v) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.14 v ss ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3 bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.1 bus read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.2 bus write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.3 output disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.4 standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.5 automatic standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6 special bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.1 read electronic signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.2 verify extended block protection indicator . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.3 verify block protection status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.4 hardware block protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6.5 temporary unprotect of high voltage protected blocks . . . . . . . . . . . . . . . . 19 4 hardware protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
m29dw128f 3/93 4.1 write protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.2 temporary block unprotect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5 software protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1 standard protection mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1.1 block lock/unlock protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1.2 non-volatile protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.2 password protection mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.2.1 block lock/unlock protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.2.2 non-volatile protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6 command interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1 standard commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.1 read/reset command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.2 auto select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.3 read cfi query command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.4 chip erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1.5 block erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1.6 erase suspend command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.1.7 erase resume command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.1.8 program suspend command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.1.9 program resume command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.1.10 program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.1.11 verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 6.2 fast program commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.2.1 write to buffer and program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.2.2 write to buffer and program confirm command . . . . . . . . . . . . . . . . . . . . . . 34 6.2.3 write to buffer and program abort and reset command . . . . . . . . . . . . . . . 34 6.2.4 double word program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.2.5 quadruple word program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.2.6 double byte program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.2.7 quadruple byte program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2.8 octuple byte program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2.9 unlock bypass command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.2.10 unlock bypass program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.2.11 unlock bypass reset command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
m29dw128f 4/93 6.3 block protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.3.1 enter extended block command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.3.2 exit extended block command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3.3 set extended block protection bit command . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3.4 verify extended block protection bit command . . . . . . . . . . . . . . . . . . . . . . 38 6.3.5 password program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3.6 password verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.3.7 password protection unlock command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.3.8 set password protection mode command . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.3.9 verify password protection mode command . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.3.10 set standard protection mode command . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.3.11 verify standard protection mode command . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.3.12 set non-volatile modify protection bit command . . . . . . . . . . . . . . . . . . . . . 40 6.3.13 verify non-volatile modify protection bit command . . . . . . . . . . . . . . . . . . . 41 6.3.14 clear non-volatile modify protection bits command . . . . . . . . . . . . . . . . . . . 41 6.3.15 set lock bit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.3.16 clear lock bit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.3.17 verify lock bit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.3.18 set lock-down bit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.3.19 verify lock-down bit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 7 status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.1 data polling bit (dq7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.2 toggle bit (dq6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.3 error bit (dq5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 7.4 erase timer bit (dq3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 7.5 alternative toggle bit (dq2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 7.6 write to buffer and program abort bit (dq1) . . . . . . . . . . . . . . . . . . . . . . . . 46 8 dual operations and multiple bank architecture . . . . . . . . . . . . . . . . . . . 49 9 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 10 dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 11 package mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
m29dw128f 5/93 12 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 appendix a block addresses and read/modify protection groups. . . . . . . . . . 67 appendix b common flash interface (cfi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 appendix c extended memory block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 c.1 factory locked section of the extended block . . . . . . . . . . . . . . . . . . . . . . . 82 c.2 customer lockable section of the extended block . . . . . . . . . . . . . . . . . . . . 82 appendix d high voltage block protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 d.1 programmer technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 d.2 in-system technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 appendix e flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 13 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
m29dw128f 6/93 list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 2. bank architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 table 3. bus operations, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 4. read electronic signature, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 5. block protection, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 6. bus operations, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 7. read electronic signature, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 8. block protection, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 9. hardware protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 10. block protection status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 11. standard commands, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 table 12. standard commands, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 13. fast program commands, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 14. fast program commands, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 15. block protection commands, 8-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 16. block protection commands, 16-bit mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 17. protection command addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4 table 18. program, erase times and program, erase endurance cycles. . . . . . . . . . . . . . . . . . . . . 44 table 19. status register bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 20. dual operations allowed in other banks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 table 21. dual operations allowed in same bank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 table 22. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 table 23. operating and ac measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 table 24. device capacitance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 25. dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 26. read ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 table 27. write ac characteristics, write enable controlled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 table 28. write ac characteristics, chip enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 table 29. toggle and alternative toggle bits ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 30. reset/block temporary unprotect ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 table 31. tsop56 ? 56 lead plastic thin small outline, 14 x 20mm, package mechanical data. . . 64 table 32. tbga64 10x13mm - 8x8 active ball array, 1mm pitch, package mechanical data . . . . . . 65 table 33. ordering information scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 table 34. block addresses and protection groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 35. query structure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 36. cfi query identification string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 table 37. cfi query system interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 table 38. device geometry definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 table 39. primary algorithm-specific extended query table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 table 40. security code area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 table 41. extended block address and data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3 table 42. programmer technique bus operations, 8-bit or 16-bit mode . . . . . . . . . . . . . . . . . . . . . . 85 table 43. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
m29dw128f 7/93 list of figures figure 1. logic diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 2. tsop connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 3. tbga connections (top view through package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 4. block addresses (x8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 5. block addresses (x16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 6. block protection state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 7. software protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 8. data polling flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 figure 9. toggle flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 figure 10. ac measurement i/o waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 figure 11. ac measurement load circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 figure 12. random read ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4 figure 13. page read ac waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 figure 14. write ac waveforms, write enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 figure 15. write ac waveforms, chip enable controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 figure 16. toggle and alternative toggle bits mechanism, chip enable controlled. . . . . . . . . . . . . . 61 figure 17. toggle and alternative toggle bits mechanism, output enable controlled . . . . . . . . . . . . 61 figure 18. reset/block temporary unprotect ac waveforms (no program/erase ongoing). . . . . . . 62 figure 19. reset/block temporary unprotect during program/erase operation ac waveforms . . . . 62 figure 20. accelerated program timing waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 figure 21. tsop56 ? 56 lead plastic thin small outline, 14 x 20mm, package outline . . . . . . . . . . 64 figure 22. tbga64 10x13mm - 8x8 active ball array, 1mm pitch, package outline . . . . . . . . . . . . . . 65 figure 23. programmer equipment group protect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 figure 24. programmer equipment chip unprotect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 figure 25. in-system equipment group protect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 figure 26. in-system equipment chip unprotect flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 figure 27. write to buffer and program flowchart and pseudo code. . . . . . . . . . . . . . . . . . . . . . . . . 90
1 summary description m29dw128f 8/93 1 summary description the m29dw128f is a 128 mbit (16mb x8 or 8mb x16) non-volatile memory that can be read, erased and reprogrammed. these operations can be performed using a single low voltage (2.7 to 3.6v) supply. v ccq is an additional voltage supply that allows to drive the i/o pins down to 1.65v. at power-up the memory defaults to its read mode. the m29dw128f features an asymmetrical block architecture, with 16 parameter and 254 main blocks, divided into four banks, a, b, c and d, providing multiple bank operations. while programming or erasing in one bank, read operations are possible in any other bank. the bank architecture is summarized in ta bl e 2 . eight of the parameter blocks are at the top of the memory address space, and eight are at the bottom. program and erase commands are written to the command interface of the memory. an on- chip program/erase controller simplifies the process of programming or erasing the memory by taking care of all of the special operations that are required to update the memory contents. the end of a program or erase operation can be detected and any error conditions identified. the command set required to control the memory is consistent with jedec standards. the chip enable, output enable and write enable signals control the bus operations of the memory. they allow simple connection to most microprocessors, often without additional logic. the device supports asynchronous random read and page read from all blocks of the memory array. the m29dw128f has one extra 256 byte block (extended block) that can be accessed using a dedicated command. the extended block can be protected and so is useful for storing security information. however the protection is irreversible, once protected the protection cannot be undone. each block can be erased independently, so it is possible to preserve valid data while old data is erased. the device features four different levels of hardware and software block protection to avoid unwanted program or erase (modify). the software block protection features are available in 16 bit memory organization only: hardware protection: ?the v pp /wp provides a hardware protection of the four outermost parameter blocks (two at the top and two at the bottom of the address space). ?the rp pin temporarily unprotects all the blocks previously protected using a high voltage block protection technique (see appendix d: high voltage block protection ). software protection ? standard protection ? password protection the memory is offered in tsop56 (14 x 20mm) and tbga64 (10 x 13mm, 1mm pitch) packages. the 8-bit bus mode is only available when the m29dw128f is delivered in tsop56 package. in order to meet environmental requirements, st offers the m29dw128f in ecopack ? packages. ecopack packages are lead-free. the category of second level interconnect is marked on the package and on the inner box label, in compliance with jedec standard jesd97. the maximum ratings related to soldering conditions are also marked on the inner box label. ecopack is an st trademark. ecopack specifications are available at: www.st.com. the memory is supplied with all the bits erased (set to ?1?).
m29dw128f 1 summary description 9/93 table 1. signal names figure 1. logic diagram a0-a22 address inputs dq0-dq7 data inputs/outputs dq8-dq14 data inputs/outputs dq15a?1 data input/output or address input e chip enable g output enable w write enable rp reset/block temporary unprotect rb ready/busy output byte byte/word organization select (1) 1. the x8 organization is only available in tsop56 package while the x16 organization is available for both packages. v cc supply voltage v ccq supply voltage for input/outputs v pp /wp v pp /write protect v ss ground nc not connected internally ai09208 23 a0-a22 w dq0-dq14 v cc m29dw128f e v ss 15 g rp dq15a?1 rb v pp /wp byte v ccq
1 summary description m29dw128f 10/93 table 2. bank architecture figure 2. tsop connections bank bank size parameter blocks main blocks no. of blocks block size no. of blocks block size a 16 mbit 8 8 kbytes/ 4 kwords 31 64 kbytes/ 32 kwords b 48 mbit ? ? 96 64 kbytes/ 32 kwords c 48 mbit ? ? 96 64 kbytes/ 32 kwords d 16 mbit 8 8 kbytes/ 4 kwords 31 64 kbytes/ 32 kwords dq3 dq9 dq2 a6 dq0 w a3 rb dq6 a19 a8 dq13 a17 a12 dq14 a2 dq12 dq10 dq15a?1 v cc dq4 dq5 a7 dq7 v pp /wp a21 ai09209b m29dw128f 14 1 15 28 29 42 43 56 dq8 nc a20 a1 a18 a4 a5 dq1 dq11 g a14 a15 a16 a13 byte nc a22 v ss e a0 rp v ss a9 a10 a11 nc nc nc nc v ccq
m29dw128f 1 summary description 11/93 figure 3. tbga connections (top view through package) 6 5 4 3 2 1 v ss a11 a10 a8 a9 dq3 dq11 dq10 a18 v pp / wp rb a0 a2 a4 a3 g nc nc nc dq2 dq1 dq9 dq8 a6 a17 a7 dq4 v cc dq12 dq5 a19 a21 rp w a5 dq0 nc nc v ss a1 a20 dq7 nc c b a e d f g h dq15 8 7 ai09210b nc a15 a14 a12 a13 dq6 dq13 dq14 nc a22 nc v ss a16 nc nc e nc nc v ccq v ccq
1 summary description m29dw128f 12/93 figure 4. block addresses (x8) 1. also see appendix a and table 34 for a full listing of the block addresses. ai08966 64 kbytes 800000h 80ffffh 64 kbytes fe0000h feffffh (x8) address lines a22-a0, dq15a-1 64 kbytes df0000h dfffffh total of 96 main blocks 64 kbytes e00000h e0ffffh 8 kbytes ffe000h ffffffh 8 kbytes ff0000h ff1fffh total of 31 main blocks total of 8 parameter blocks bank c bank d 8 kbytes 000000h 001fffh 64 kbytes 1f0000h 1fffffh 8 kbytes 00e000h 00ffffh total of 8 parameter blocks 64 kbytes 010000h 01ffffh 64 kbytes 7f0000h 7fffffh 64 kbytes 200000h 20ffffh total of 31 main blocks total of 96 main blocks bank b bank a
m29dw128f 1 summary description 13/93 figure 5. block addresses (x16) 1. also see appendix a , table 34 for a full listing of the block addresses. ai08967 32 kwords 400000h 407fffh 32 kwords 7f0000h 7f7fffh (x16) address lines a22-a0 32 kwords 6f8000h 6fffffh total of 96 main blocks 32 kwords 700000h 707fffh 4 kwords 7ff000h 7fffffh 4 kwords 7f8000h 7f8fffh total of 31 main blocks total of 8 parameter blocks bank c bank d 4 kwords 000000h 000fffh 32 kwords 0f8000h 0fffffh 4 kwords 007000h 007fffh total of 8 parameter blocks 32 kwords 008000h 00ffffh 32 kwords 3f8000h 3fffffh 32 kword 100000h 107fffh total of 31 main blocks total of 96 main blocks bank b bank a
2 signal descriptions m29dw128f 14/93 2 signal descriptions see figure 1: logic diagram , and table 1: signal names , for a brief overview of the signals connected to this device. 2.1 address inputs (a0-a22) the address inputs select the cells in the memory array to access during bus read operations. during bus write operations they control the commands sent to the command interface of the program/erase controller. 2.2 data inputs/outputs (dq0-dq7) the data i/o outputs the data stored at the selected address during a bus read operation. during bus write operations they represent the commands sent to the command interface of the internal state machine. 2.3 data inputs/outputs (dq8-dq14) the data i/o outputs the data stored at the selected address during a bus read operation when byte is high, v ih . when byte is low, v il , these pins are not used and are high impedance. during bus write operations the command register does not use these bits. when reading the status register these bits should be ignored. 2.4 data input/output or address input (dq15a?1) when the device is in x16 bus mode, this pin behaves as a data input/output pin (as dq8- dq14). when the device is in x8 bus mode, this pin behaves as an address pin; dq15a?1 low will select the lsb of the addressed word, dq15a?1 high will select the msb. throughout the text consider references to the data input/output to include this pin when the device operates in x16 bus mode and references to the address inputs to include this pin when the device operates in x8 bus mode except when stated explicitly otherwise. 2.5 chip enable (e ) the chip enable pin, e , activates the memory, allowing bus read and bus write operations to be performed. when chip enable is high, v ih , all other pins are ignored. 2.6 output enable (g ) the output enable pin, g , controls the bus read operation of the memory.
m29dw128f 2 signal descriptions 15/93 2.7 write enable (w ) the write enable pin, w , controls the bus write operation of the memory?s command interface. 2.8 v pp/ write protect (v pp /wp ) the v pp /write protect pin provides two functions. the v pp function allows the memory to use an external high voltage power supply to reduce the time required for program operations. this is achieved by bypassing the unlock cycles and/or using the multiple word (2 or 4 at-a-time) or multiple byte program (2, 4 or 8 at-a-time) commands. the write protect function provides a hardware method of protecting the four outermost boot blocks (two at the top, and two at the bottom of the address space). when v pp /write protect is low, v il , the memory protects the four outermost boot blocks; program and erase operations in these blocks are ignored while v pp /write protect is low, even when rp is at v id . when v pp /write protect is high, v ih , the memory reverts to the previous protection status of the four outermost boot blocks. program and erase operations can now modify the data in these blocks unless the blocks are protected using block protection. applying v pph to the v pp /wp pin will temporarily unprotect any block previously protected (including the four outermost parameter blocks) using a high voltage block protection technique (in-system or programmer technique). see table 9: hardware protection for details. when v pp /write protect is raised to v pp the memory automatically enters the unlock bypass mode. when v pp /write protect returns to v ih or v il normal operation resumes. during unlock bypass program operations the memory draws i pp from the pin to supply the programming circuits. see the description of the unlock bypass command in the command interface section. the transitions from v ih to v pp and from v pp to v ih must be slower than t vhvpp , see figure 20 . never raise v pp /write protect to v pp from any mode except read mode, otherwise the memory may be left in an indeterminate state. the v pp /write protect pin must not be left floating or unconnected or the device may become unreliable. a 0.1f capacitor should be connected between the v pp /write protect pin and the v ss ground pin to decouple the current surges from the power supply. the pcb track widths must be sufficient to carry the currents required during unlock bypass program, i pp . 2.9 reset/block temporary unprotect (rp ) the reset/block temporary unprotect pin can be used to apply a hardware reset to the memory or to temporarily unprotect all the blocks previously protected using a high voltage block protection technique (in-system or programmer technique). note that if v pp /wp is at v il , then the four outermost parameter blocks will remain protected even if rp is at v id . a hardware reset is achieved by holding reset/block temporary unprotect low, v il , for at least t plpx . after reset/block temporary unprotect goes high, v ih , the memory will be ready for bus read and bus write operations after t phel or t rhel , whichever occurs last. see the ready/busy output section, table 30: reset/block temporary unprotect ac characteristics and figure 18 and figure 19 for more details.
2 signal descriptions m29dw128f 16/93 holding rp at v id will temporarily unprotect all the blocks previously protected using a high voltage block protection technique. program and erase operations on all blocks will be possible. the transition from v ih to v id must be slower than t phphh . 2.10 ready/busy output (rb ) the ready/busy pin is an open-drain output that can be used to identify when the device is performing a program or erase operation. during program or erase operations ready/busy is low, v ol . ready/busy is high-impedance during read mode, auto select mode and erase suspend mode. after a hardware reset, bus read and bus write operations cannot begin until ready/busy becomes high-impedance. see table 30: reset/block temporary unprotect ac characteristics and figure 18 and figure 19 . the use of an open-drain output allows the ready/busy pins from several memories to be connected to a single pull-up resistor. a low will then indicate that one, or more, of the memories is busy. 2.11 byte/word organization select (byte ) it is used to switch between the x8 and x16 bus modes of the memory when the m29dw128f is delivered in tsop56 package. when byte/word organization select is low, v il , the memory is in x8 mode, when it is high, v ih , the memory is in x16 mode. 2.12 v ccq supply voltage v ccq provides the power supply to the i/o and control pins and enables all outputs to be powered independently from v cc . v ccq can be tied to v cc or can use a separate supply. 2.13 v cc supply voltage (2.7v to 3.6v) v cc provides the power supply for all operations (read, program and erase). the command interface is disabled when the v cc supply voltage is less than the lockout voltage, v lko . this prevents bus write operations from accidentally damaging the data during power up, power down and power surges. if the program/erase controller is programming or erasing during this time then the operation aborts and the memory contents being altered will be invalid. a 0.1f capacitor should be connected between the v cc supply voltage pin and the v ss ground pin to decouple the current surges from the power supply. the pcb track widths must be sufficient to carry the currents required during program and erase operations, i cc2 . 2.14 v ss ground v ss is the reference for all voltage measurements. the device features two v ss pins both of which must be connected to the system ground.
m29dw128f 3 bus operations 17/93 3 bus operations there are five standard bus operations that control the device. these are bus read (random and page modes), bus write, output disable, standby and automatic standby. dual operations are possible in the m29dw128f, thanks to its multiple bank architecture. while programming or erasing in one banks, read operations are possible in any of the other banks. write operations are only allowed in one bank at a time. see ta b l e 3 and ta b l e 6 , bus operations, for a summary. typically glitches of less than 5ns on chip enable, write enable, and reset/block temporary unprotect pins are ignored by the memory and do not affect bus operations. 3.1 bus read bus read operations read from the memory cells, or specific registers in the command interface. to speed up the read operation the memory array can be read in page mode where data is internally read and stored in a page buffer. the page has a size of 8 words and is addressed by the address inputs a0-a2. a valid bus read operation involves setting the desired address on the address inputs, applying a low signal, v il , to chip enable and output enable and keeping write enable high, v ih . the data inputs/outputs will output the value, see figure 12: random read ac waveforms , figure 13: page read ac waveforms , and table 26: read ac characteristics , for details of when the output becomes valid. 3.2 bus write bus write operations write to the command interface. a valid bus write operation begins by setting the desired address on the address inputs. the address inputs are latched by the command interface on the falling edge of chip enable or write enable, whichever occurs last. the data inputs/outputs are latched by the command interface on the rising edge of chip enable or write enable, whichever occurs first. output enable must remain high, v ih , during the whole bus write operation. see figure 14 and figure 15 , write ac waveforms, and ta b l e 2 7 and ta b l e 2 8 , write ac characteristics, for details of the timing requirements. 3.3 output disable the data inputs/outputs are in the high impedance state when output enable is high, v ih . 3.4 standby when chip enable is high, v ih , the memory enters standby mode and the data inputs/outputs pins are placed in the high-impedance state. to reduce the supply current to the standby supply current, i cc2 , chip enable should be held within v cc 0.2v. for the standby current level see table 25: dc characteristics . during program or erase operations the memory will continue to use the program/erase supply current, i cc3 , for program or erase operations until the operation completes.
3 bus operations m29dw128f 18/93 3.5 automatic standby if cmos levels (v cc 0.2v) are used to drive the bus and the bus is inactive for 300ns or more the memory enters automatic standby where the internal supply current is reduced to the standby supply current, i cc2 . the data inputs/outputs will still output data if a bus read operation is in progress. 3.6 special bus operations additional bus operations can be performed to read the electronic signature, verify the protection status of the extended memory block (second section), and apply and remove block protection. these bus operations are intended for use by programming equipment and are not usually used in applications. they require v id to be applied to some pins. 3.6.1 read electronic signature the memory has two codes, the manufacturer code and the device code used to identify the memory. these codes can accessed by performing read operations with control signals and addresses set as shown in ta bl e 4 and ta b l e 6 . these codes can also be accessed by issuing an auto select command (see auto select command in section 6: command interface ). 3.6.2 verify extended bloc k protection indicator the extended block is divided in two sections of which one is factory locked and the second one is either customer lockable or customer locked. the protection status of the second section of the extended block (customer lockable or customer locked) can be accessed by reading the extended block protection indicator. this is performed by applying the signals as shown in ta b l e 5 and ta b l e 8 . the protection status of the extended block is then output on bits dq7 and dq6 of the data input/outputs. (see ta b l e 3 and ta b l e 6 , bus operations). the protection status of the extended block can also be accessed by issuing an auto select command (see auto select command in section 6: command interface ). 3.6.3 verify block protection status the protection status of a block can be directly accessed by performing a read operation with control signals and addresses set as shown in ta b l e 5 and ta bl e 8 . if the block is protected, then 01h (in x8 mode) is output on data input/outputs dq0-dq7, otherwise 00h is output. 3.6.4 hardware block protect the v pp /wp pin can be used to protect the four outermost parameter blocks. when v pp /wp is at v il the four outermost parameter blocks are protected and remain protected regardless of the block protection status or the reset/block temporary unprotect pin state.
m29dw128f 3 bus operations 19/93 3.6.5 temporary unprotect of high voltage protected blocks the rp pin can be used to temporarily unprotect all the blocks previously protected using the in-system or the programmer protection technique (high voltage techniques). refer to reset/block temporary unprotect (rp) in section 2: signal descriptions . table 3. bus operations, 8-bit mode table 4. read electronic signature, 8-bit mode operation (1) 1. x = v il or v ih . e g w rp v pp /wp address inputs data inputs/outputs a22-a0, dq15a-1 dq14-dq8 dq7-dq0 bus read v il v il v ih v ih v ih cell address hi-z data output bus write v il v ih v il v ih v ih command address hi-z data input output disable x v ih v ih v ih v ih x hi-z hi-z standby v ih xx v ih v ih x hi-z hi-z read cycle (1) 1. x = v il or v ih . e g w address inputs data inputs/ outputs a22- a10 a9 a8 a7- a6 a5- a4 a3 a2 a1 a0 dq15a -1 dq14- dq8 dq7- dq0 manufacturer code v il v il v ih x v id x v il x v il v il v il v il xhi-z20h device code (cycle 1) v il v il v il v il v ih xhi-z7eh device code (cycle 2) v ih v ih v ih v il xhi-z20h device code (cycle 3) v ih v ih v ih v ih xhi-z00h
3 bus operations m29dw128f 20/93 table 5. block protection, 8-bit mode table 6. bus operations, 16-bit mode table 7. read electronic signature, 16-bit mode operation (1) 1. x = v il or v ih . e g w rp v pp / wp address inputs (2) 2. bka bank address, ba any address in the block. data inputs/outputs a22- a12 a11- a10 a9 a8 a7 a6 a5- a4 a3- a2 a1 a0 dq15a -1 dq14- dq8 dq7-dq0 verify extended block protection indicator (bits dq6, dq7) v il v il v ih v ih v ih ba x v id x x v il x v il v ih v ih x hi-z 80h (customer lockable) c0h (customer locked) (3) 3. this indicates the protection status of the second section of the extended block; the first section of the extended block being always factory locked. verify block protection status bka v il v il v il x 01h (protected) 00h (unprotected) temporary block unprotect (4) 4. the rp pin unprotects all the blocks that have been previous ly protected using a high voltage protection technique. xxx v id x valid data input operation (1) 1. x = v il or v ih . e g w rp v pp / wp address inputs data inputs/outputs a22-a0 dq15a-1, dq14-dq0 bus read v il v il v ih v ih v ih cell address data output bus write v il v ih v il v ih v ih command address data input output disable x v ih v ih v ih v ih x hi-z standby v ih xx v ih v ih x hi-z read cycle (1) 1. x = v il or v ih . e g w address inputs data inputs/outputs a22- a10 a9 a8 a7- a6 a5- a4 a3 a2 a1 a0 dq15a-1, dq14-dq0 manufacturer code v il v il v ih x v id x v il x v il v il v il v il 0020h device code (cycle 1) v il v il v il v il v ih 227eh device code (cycle 2) v ih v ih v ih v il 2220h device code (cycle 3) v ih v ih v ih v ih 2200h
m29dw128f 3 bus operations 21/93 table 8. block protection, 16-bit mode operation (1) 1. x = v il or v ih . e g w rp v pp / wp address inputs (2) 2. bka bank address, ba any address in the block. data inputs/outputs a22- a12 a11- a10 a9 a8 a7 a6 a5- a4 a3- a2 a1 a0 dq15a-1, dq14-dq0 verify extended block indicator (bits dq6, dq7) v il v il v ih v ih v ih ba x v id x x v il x v il v ih v ih 0080h (customer lockable) 00c0h (customer locked) (3) 3. this indicates the protection status of the second section of the extended block; the first section of the extended block being always factory locked. verify block protection status bka v il v il v il 0001h (protected) 0000h (unprotected) temporary block unprotect (4) 4. the rp pin unprotects all the blocks that have been previous ly protected using a high voltage protection technique. xxx v id x valid data input
4 hardware protection m29dw128f 22/93 4 hardware protection the m29dw128f features hardware protection/unprotection. refer to ta bl e 9 for details on hardware block protection/unprotection using v pp /wp and rp pins. 4.1 write protect the v pp /wp pin protects the four outermost parameter blocks (refer to section 2: signal descriptions for a detailed description of the signals). 4.2 temporary block unprotect when held at v id , the reset/block temporary unprotect pin, rp , will temporarily unprotect all the blocks previously protected using a high voltage block protection technique. table 9. hardware protection v pp /wp rp function v il v ih 4 outermost parameter blocks protected from program/erase operations v id all blocks temporarily unprotected except the 4 outermost blocks (1) 1. the temporary unprotection is valid only for the blocks that have been protected using the high voltage protection technique (see appendix d: high voltage block protection ). the blocks protected using a software protection method (standard, password) do not follow this rules. v ih or v id v id all blocks temporarily unprotected (1) v pph v ih or v id all blocks temporarily unprotected (1)
m29dw128f 5 software protection 23/93 5 software protection the m29dw128f has two different software protection modes: the standard protection mode and the password protection mode. on first use all parts default to the standard protection mode and the customer is free to activate the standard or the password protection mode. the desired protection mode is activated by setting one of two one-time programmable bits, the standard protection mode lock bit or the password protection mode lock bit. programming the standard and the password protection mode lock bit to ?1? will permanently activate the standard protection mode and the password protection mode, respectively. these two bits are one-time programmable and non-volatile, once the protection mode has been programmed, it cannot be changed and the device will permanently operate in the selected protection mode. it is recommended to activate the desired software protection mode when first programming the device. the device is shipped with all blocks unprotected. the block protection status can be read by issuing the auto select command (see table 10: block protection status ). the standard and password protection modes offer two levels of protection, a block lock/ unlock protection and a non-volatile protection. for the four outermost parameter blocks, an even higher level of block protection can be achieved by locking the blocks using the non-volatile protection and then by holding the v pp / wp pin low. 5.1 standard protection mode 5.1.1 block lock/unlock protection it is a flexible mechanism to protect/unprotect a block or a group of blocks from program or erase operations. a volatile lock bit is assigned to each block or group of blocks. when the lock bit is set to ?1? the associated block or group of blocks is protected from program/erase operations, when the lock bit is set to ?0? the associated block or group of blocks is unprotected and can be programmed or erased. the lock bits can be set (?1?) and cleared (?0?) individually as often as required by issuing a set lock bit command and clear lock bit command, respectively. after a power-up or hardware reset, all the lock bits are cleared to ?0? (block unlocked). 5.1.2 non-volatile protection a non-volatile modify protection bit is assigned to each block or group of blocks. when a non-volatile modify protection bit is set to ?1? the associated block or group of blocks is protected, preventing any program or erase operations in this block or group of blocks. the non-volatile modify protection bits are set individually by issuing a set non-volatile modify protection bit command. they are non-volatile and will remain set through a hardware reset or a power-down/power-up sequence.
5 software protection m29dw128f 24/93 the non-volatile modify protection bits cannot be cleared individually, they can only be cleared all at the same time by issuing a clear non-volatile modify protection bits command. however if any one of the non-volatile modify protection bits has to be cleared, care should be taken to preprogram to ?1? all the non-volatile modify protection bits prior to issuing the clear non-volatile modify protection bits in order to prevent the over-erasure of previously cleared non volatile modify protection bits. it is crucial to prevent over-erasure because the process may lead to permanent damage to the non-volatile modify protection bits and the device does not have any built-in means of preventing over-erasure. the device features a volatile lock-down bit which can be used to prevent changing the state of the non-volatile modify protection bits. when set to ?1?, the non-volatile modify protection bits can no longer be modified; when set to ?0?, the non-volatile modify protection bits can be set and reset using the set non-volatile modify protection bit command and the clear non- volatile modify protection bits command, respectively. the lock-down bit is set by issuing the set lock-down bit command. it is not cleared using a command, but through a hardware reset or a power-down/power-up sequence. the parts are shipped with the non-volatile modify protection bits set to ?0?. locked blocks and non-volatile locked blocks can co-exist in the same memory array. refer to table 10: block protection status and figure 7: software protection scheme for details on the block protection mechanism. 5.2 password protection mode the password protection mode provides a more advanced level of software protection than the standard protection mode. prior to entering the password protection mode, it is necessary to set a password and to verify it (see password program command and password verify command ). the password protection mode is then activated by programming the password protection mode lock bit to ?1?. the reset/block temporary unprotect pin, rp , can be at v id or at v ih . this operation is not reversible and once the bit is programmed the device will permanently remain in the password protection mode. the password protection mode uses the same protection mechanisms as the standard protection mode (block lock/unlock, non-volatile protection). 5.2.1 block lock/unlock protection the block lock/unlock protection operates exactly in the same way as in the standard protection mode. 5.2.2 non-volatile protection the non-volatile protection is more advanced in the password protection mode. in this mode, the lock-down bit cannot be cleared through a hardware reset or a power-down/ power-up sequence. the lock-down bit is cleared by issuing the password protection unlock command along with the correct password.
m29dw128f 5 software protection 25/93 once the correct password has been provided, the lock-down bit is cleared and the non- volatile modify protection bits can be set or reset using the appropriate commands (the set non-volatile modify protection bit command or the clear non-volatile modify protection bits command, respectively). if the password provided is not correct, the lock-down bit remains locked and the state of the non-volatile modify protection bits cannot be modified. the password is a 64-bit code located in the memory space. it must be programmed by the user prior to selecting the password protection mode. the password is programmed by issuing a password program command and checked by issuing a password verify command. the password should be unique for each part. once the device is in password protection mode, the password can no longer be read or retrieved. moreover, all commands to the address where the password is stored, are disabled. refer to table 10: block protection status and figure 7: software protection scheme for details on the block protection scheme. table 10. block protection status figure 6. block protection state diagram volatile lock bit non- volatile modify protection bit lock- down bit block protectio n status block protection status 00 0 00h block unprotected non-volatile modify protection bit can be modified (1) 1. the lock bit can always be modified by issuing a clear lo ck bit command or by taking the device through a power-up or hardware reset. 00 1 non-volatile modify protection bit cannot be modified (1) 01 0 01h block program/ erase protected non-volatile modify protection bit can be modified (1) 10 0 11 0 01 1 non-volatile modify protection bit cannot be modified (1) 10 1 11 1 ai11503 set standard protection mode default: standard protection password protection standard protection set password protection mode
5 software protection m29dw128f 26/93 figure 7. software protection scheme ai11504 parameter block or up to 4 main blocks non-volatile modify protection bit lock bit standard protection mode block lock/unlock protection non-volatile protection password protection mode lock-down bit
m29dw128f 6 command interface 27/93 6 command interface all bus write operations to the memory are interpreted by the command interface. commands consist of one or more sequential bus write operations. failure to observe a valid sequence of bus write operations will result in the memory returning to read mode. the long command sequences are imposed to maximize data security. the address used for the commands changes depending on whether the memory is in 16-bit or 8-bit mode. 6.1 standard commands see either ta b l e 1 2 , or ta b l e 1 1 , depending on the configuration that is being used, for a summary of the standard commands. 6.1.1 read/reset command the read/reset command returns the memory to read mode. it also resets the errors in the status register. either one or three bus write operations can be used to issue the read/reset command. the read/reset command can be issued, between bus write cycles before the start of a program or erase operation, to return the device to read mode. if the read/reset command is issued during the time-out of a block erase operation, the memory will take up to 10s to abort. during the abort period no valid data can be read from the memory. the read/reset command will not abort an erase operation when issued while in erase suspend. 6.1.2 auto select command the auto select command is used to read the manufacturer code, the device code, the protection status of each block (block protection status) and the extended block protection indicator. it can be addressed to either bank. three consecutive bus write operations are required to issue the auto select command. once the auto select command is issued bus read operations to specific addresses output the manufacturer code, the device code, the extended block protection indicator and a block protection status (see ta b l e 1 1 and ta bl e 1 2 in conjunction with ta b l e 4 , ta b l e 5 , ta bl e 7 and ta b l e 8 ). the memory remains in auto select mode until a read/reset or cfi query command is issued. 6.1.3 read cfi query command the read cfi query command is used to put the addressed bank in read cfi query mode. once in read cfi query mode bus read operations to the same bank will output data from the common flash interface (cfi) memory area. if the read operations are to a different bank from the one specified in the command then the read operations will output the contents of the memory array and not the cfi data. one bus write cycle is required to issue the read cfi query command. care must be taken to issue the command to one of the banks (a22-a19) along with the address shown in ta bl e 3 and
6 command interface m29dw128f 28/93 ta b l e 6 . once the command is issued subsequent bus read operations in the same bank (a22-a19) to the addresses shown in appendix b: common flash interface (cfi) (a7-a0), will read from the common flash interface memory area. this command is valid only when the device is in the read array or auto select mode. to enter read cfi query mode from auto select mode, the read cfi query command must be issued to the same bank address as the auto select command, otherwise the device will not enter read cfi query mode. the read/reset command must be issued to return the device to the previous mode (the read array mode or auto select mode). a second read/reset command is required to put the device in read array mode from auto select mode. see appendix b , ta b l e 3 5 , ta bl e 3 6 , ta b l e 3 7 , ta b l e 3 8 , ta b l e 3 9 and ta bl e 4 0 for details on the information contained in the common flash interface (cfi) memory area. 6.1.4 chip erase command the chip erase command can be used to erase the entire chip. six bus write operations are required to issue the chip erase command and start the program/erase controller. if any blocks are protected, then these are ignored and all the other blocks are erased. if all of the blocks are protected the chip erase operation appears to start but will terminate within about 100s, leaving the data unchanged. no error condition is given when protected blocks are ignored. during the erase operation the memory will ignore all commands, including the erase suspend command. it is not possible to issue any command to abort the operation. typical chip erase times are given in ta b l e 1 8 . all bus read operations during the chip erase operation will output the status register on the data inputs/outputs. see the section on the status register for more details. after the chip erase operation has completed the memory will return to the read mode, unless an error has occurred. when an error occurs the memory will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. the chip erase command sets all of the bits in unprotected blocks of the memory to ?1?. all previous data is lost. 6.1.5 block erase command the block erase command can be used to erase a list of one or more blocks in one or more banks. it sets all of the bits in the unprotected selected blocks to ?1?. all previous data in the selected blocks is lost. six bus write operations are required to select the first block in the list. each additional block in the list can be selected by repeating the sixth bus write operation using the address of the additional block. the block erase operation starts the program/erase controller after a time- out period of 50s after the last bus write operation. once the program/erase controller starts it is not possible to select any more blocks. each additional block must therefore be selected within 50s of the last block. the 50s timer restarts when an additional block is selected. after the sixth bus write operation a bus read operation within the same bank will output the status register. see the status register section for details on how to identify if the program/erase controller has started the block erase operation.
m29dw128f 6 command interface 29/93 if any selected blocks are protected then these are ignored and all the other selected blocks are erased. if all of the selected blocks are protected the block erase operation appears to start but will terminate within about 100s, leaving the data unchanged. no error condition is given when protected blocks are ignored. during the block erase operation the memory will ignore all commands except the erase suspend command and the read/reset command which is only accepted during the 50s time-out period. typical block erase times are given in ta b l e 1 8 . after the erase operation has started all bus read operations to the banks being erased will output the status register on the data inputs/outputs. see the section on the status register for more details. after the block erase operation has completed the memory will return to the read mode, unless an error has occurred. when an error occurs, bus read operations to the banks where the command was issued will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. 6.1.6 erase suspend command the erase suspend command may be used to temporarily suspend a block or multiple block erase operation. one bus write operation specifying the bank address of one of the blocks being erased is required to issue the command. issuing the erase suspend command returns the whole device to read mode. the program/erase controller will suspend within the erase suspend latency time (see ta b l e 1 8 for value) of the erase suspend command being issued. once the program/erase controller has stopped the memory will be set to read mode and the erase will be suspended. if the erase suspend command is issued during the period when the memory is waiting for an additional block (before the program/erase controller starts) then the erase is suspended immediately and will start immediately when the erase resume command is issued. it is not possible to select any further blocks to erase after the erase resume. during erase suspend it is possible to read and program cells in blocks that are not being erased; both read and program operations behave as normal on these blocks. if any attempt is made to program in a protected block or in the suspended block then the program command is ignored and the data remains unchanged. the status register is not read and no error condition is given. reading from blocks that are being erased will output the status register. it is also possible to issue the auto select, read cfi query and unlock bypass commands during an erase suspend. the read/reset command must be issued to return the device to read array mode before the resume command will be accepted. during erase suspend a bus read operation to the extended block will output the extended block data. once in the extended block mode, the exit extended block command must be issued before the erase operation can be resumed. 6.1.7 erase resume command the erase resume command is used to restart the program/erase controller after an erase suspend. the command must include the bank address of the erase-suspended bank, otherwise the program/erase controller is not restarted. the device must be in read array mode before the resume command will be accepted. an erase can be suspended and resumed more than once.
6 command interface m29dw128f 30/93 6.1.8 program suspend command the program suspend command allows the system to interrupt a program operation so that data can be read from any block. when the program suspend command is issued during a program operation, the device suspends the program operation within the program suspend latency time (see ta bl e 1 8 for value) and updates the status register bits. the bank addresses of the block being programmed must be specified in the program suspend command. after the program operation has been suspended, the system can read array data from any address. however, data read from program-suspended addresses is not valid. the program suspend command may also be issued during a program operation while an erase is suspended. in this case, data may be read from any addresses not in erase suspend or program suspend. if a read is needed from the extended block area (one-time program area), the user must use the proper command sequences to enter and exit this region. the system may also issue the auto select command sequence when the device is in the program suspend mode. the system can read as many auto select codes as required. when the device exits the auto select mode, the device reverts to the program suspend mode, and is ready for another valid operation. see auto select command sequence for more information. 6.1.9 program resume command after the program resume command is issued, the device reverts to programming. the controller can determine the status of the program operation using the dq7 or dq6 status bits, just as in the standard program operation. see write operation status for more information. the system must write the program resume command, specifying the bank addresses of the program-suspended block, to exit the program suspend mode and to continue the programming operation. further issuing of the resume command is ignored. another program suspend command can be written after the device has resumed programming. 6.1.10 program command the program command can be used to program a value to one address in the memory array at a time. the command requires four bus write operations, the final write operation latches the address and data in the internal state machine and starts the program/erase controller. programming can be suspended and then resumed by issuing a program suspend command and a program resume command, respectively (see program suspend command and program resume command paragraphs). if the address falls in a protected block then the program command is ignored, the data remains unchanged. the status register is never read and no error condition is given. after programming has started, bus read operations in the bank being programmed output the status register content, while bus read operations to the other bank output the contents of the memory array. see the section on the status register for more details. typical program times are given in ta b l e 1 8 . after the program operation has completed the memory will return to the read mode, unless an error has occurred. when an error occurs bus read operations to the bank where the command was issued will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode.
m29dw128f 6 command interface 31/93 one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. 6.1.11 verify command the verify command is used to check if a block is blank or in other words, if it has been successfully erased and all its bits set to ?1?. it reads the value of the error bit dq5. if the error bit is set to ?1?, it indicates that the operation failed. three cycles are required to issue a verify command: 1. the command starts with two unlock cycles. 2. the third bus write cycle sets up the verify command code along with the address of the block to be checked. table 11. standard commands, 8-bit mode command length bus operations (1)(2) 1. grey cells represent read cycles . the other cells are write cycles. 2. x don?t care, pa program address, pd program data, ba any address in the block, bka bank address. all values in the table are in hexadecimal. 1st 2nd 3rd 4th 5th 6th add data add dat a add data add data add data add data read/reset 1x f0 3 aaa aa 555 55 x f0 auto select manufacturer code 3 aaa aa 555 55 (bka) aaa 90 (3) 3. the auto select addresses and data are given in table 4: read electronic signature, 8-bit mode , and table 5: block protection, 8-bit mode , except for a9 that is ?don?t care?. (3) device code extended block protection indicator block protection status program 4 aaa aa 555 55 aaa a0 pa pd verify 3 aaa aa 555 55 ba bc chip erase 6 aaa aa 555 55 aaa 80 aa a aa 555 55 aaa 10 block erase 6 + aaa aa 555 55 aaa 80 aa a aa 555 55 ba 30 erase/program suspend 1 bka b0 erase/program resume 1 bka 30 read cfi query 1 (bka) aaa 98
6 command interface m29dw128f 32/93 table 12. standard commands, 16-bit mode 6.2 fast program commands the m29dw128f offers a set of fast program commands to improve the programming throughput: write to buffer and program double and quadruple word, program double, quadruple and octuple byte program unlock bypass. see either ta b l e 1 4 , or ta b l e 1 3 , depending on the configuration that is being used, for a summary of the fast program commands. when v pph is applied to the v pp /write protect pin the memory automatically enters the fast program mode. the user can then choose to issue any of the fast program commands. care must be taken because applying a v pph to the v pp /wp pin will temporarily unprotect any protected block. only one bank can be programmed at any one time. the other bank must be in read mode or erase suspend. command length bus operations (1)(2) 1. grey cells represent read cycles . the other cells are write cycles. 2. x don?t care, pa program address, pd program data, ba any address in the block, bka bank address. all values in the table are in hexadecimal. 1st 2nd 3rd 4th 5th 6th add data add data add data add data add data add data read/reset 1xf0 3 555 aa 2aa 55 x f0 auto select manufacturer code 3 555 aa 2aa 55 (bka) 555 90 (3) 3. the auto select addresses and data are given in table 7: read electronic signature, 16-bit mode , and table 8: block protection, 16-bit mode , except for a9 that is ?don?t care?. (3) device code extended block protection indicator block protection status program 4 555 aa 2aa 55 555 a0 pa pd verify 3 555 aa 2aa 55 ba bc chip erase 6 555 aa 2aa 55 555 80 555 aa 2aa 55 555 10 block erase 6+ 555 aa 2aa 55 555 80 555 aa 2aa 55 ba 30 erase/program suspend 1 bka b0 erase/program resume 1 bka 30 read cfi query 1 (bka) 555 98
m29dw128f 6 command interface 33/93 after programming has started, bus read operations in the bank being programmed output the status register content, while bus read operations to the other bank output the contents of the memory array. fast program commands can be suspended and then resumed by issuing a program suspend command and a program resume command, respectively (see program suspend command and program resume command paragraphs.) after the fast program operation has completed, the memory will return to the read mode, unless an error has occurred. when an error occurs bus read operations to the bank where the command was issued will continue to output the status register. a read/reset command must be issued to reset the error condition and return to read mode. one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. typical program times are given in table 18: program, erase times and program, erase endurance cycles . 6.2.1 write to buffer and program command the write to buffer and program command makes use of the device?s 64-byte write buffer to speed up programming. 32 words/64 bytes can be loaded into the write buffer. each write buffer has the same a5-a22 addresses.the write to buffer and program command dramatically reduces system programming time compared to the standard non-buffered program command. when issuing a write to buffer and program command, the v pp/ wp pin can be either held high, v ih or raised to v pph . see ta bl e 1 8 for details on typical write to buffer and program times in both cases. five successive steps are required to issue the write to buffer and program command: 1. the write to buffer and program command starts with two unlock cycles. 2. the third bus write cycle sets up the write to buffer and program command. the setup code can be addressed to any location within the targeted block. 3. the fourth bus write cycle sets up the number of words to be programmed. value n is written to the same block address, where n+1 is the number of words to be programmed. n+1 must not exceed the size of the write buffer or the operation will abort. 4. the fifth cycle loads the first address and data to be programmed. 5. use n bus write cycles to load the address and data for each word into the write buffer. addresses must lie within the range from the start address+1 to the start address + n-1. optimum performance is obtained when the start address corresponds to a 64 byte boundary. if the start address is not aligned to a 64 byte boundary, the total programming time is doubled. all the addresses used in the write to buffer and program operation must lie within the same page. to program the content of the write buffer, this command must be followed by a write to buffer and program confirm command. if an address is written several times during a write to buffer and program operation, the address/data counter will be decremented at each data load operation and the data will be programmed to the last word loaded into the buffer. invalid address combinations or failing to follow the correct sequence of bus write cycles will abort the write to buffer and program.
6 command interface m29dw128f 34/93 the status register bits dq1, dq5, dq6, dq7 can be used to monitor the device status during a write to buffer and program operation. if is not possible to detect program operation fails when changing programmed data from ?0? to ?1?, that is when reprogramming data in a portion of memory already programmed. the resulting data will be the logical or between the previous value and the current value. a write to buffer and program abort and reset command must be issued to abort the write to buffer and program operation and reset the device in read mode. during write to buffer and program operations, the bank being programmed will accept program/erase suspend commands. see appendix e , figure 27: write to buffer and program flowchart and pseudo code , for a suggested flowchart on using the write to buffer and program command. 6.2.2 write to buffer and program confirm command the write to buffer and program confirm command is used to confirm a write to buffer and program command and to program the n+1 words loaded in the write buffer by this command. 6.2.3 write to buffer and program abort and reset command the write to buffer and program abort and reset command is used to abort write to buffer and program command. 6.2.4 double word program command this is used to write two adjacent words in x16 mode, simultaneously. the addresses of the two words must differ only in a0. three bus write cycles are necessary to issue the command: 1. the first bus cycle sets up the command. 2. the second bus cycle latches the address and the data of the first word to be written. 3. the third bus cycle latches the address and the data of the second word to be written and starts the program/erase controller. 6.2.5 quadruple word program command this is used to write a page of four adjacent words, in x16 mode, simultaneously. the addresses of the four words must differ only in a1 and a0. five bus write cycles are necessary to issue the command: 1. the first bus cycle sets up the command. 2. the second bus cycle latches the address and the data of the first word to be written. 3. the third bus cycle latches the address and the data of the second word to be written. 4. the fourth bus cycle latches the address and the data of the third word to be written. 5. the fifth bus cycle latches the address and the data of the fourth word to be written and starts the program/erase controller. 6.2.6 double byte program command this is used to write two adjacent bytes in x8 mode, simultaneously. the addresses of the two bytes must differ only in dq15a-1.
m29dw128f 6 command interface 35/93 three bus write cycles are necessary to issue the command: 1. the first bus cycle sets up the command. 2. the second bus cycle latches the address and the data of the first byte to be written. 3. the third bus cycle latches the address and the data of the second byte to be written and starts the program/erase controller. 6.2.7 quadruple byte program command this is used to write four adjacent bytes in x8 mode, simultaneously. the addresses of the four bytes must differ only in a0, dq15a-1. five bus write cycles are necessary to issue the command. 1. the first bus cycle sets up the command. 2. the second bus cycle latches the address and the data of the first byte to be written. 3. the third bus cycle latches the address and the data of the second byte to be written. 4. the fourth bus cycle latches the address and the data of the third byte to be written. 5. the fifth bus cycle latches the address and the data of the fourth byte to be written and starts the program/erase controller. 6.2.8 octuple byte program command this is used to write eight adjacent bytes, in x8 mode, simultaneously. the addresses of the eight bytes must differ only in a1, a0 and dq15a-1. nine bus write cycles are necessary to issue the command: 1. the first bus cycle sets up the command. 2. the second bus cycle latches the address and the data of the first byte to be written. 3. the third bus cycle latches the address and the data of the second byte to be written. 4. the fourth bus cycle latches the address and the data of the third byte to be written. 5. the fifth bus cycle latches the address and the data of the fourth byte to be written. 6. the sixth bus cycle latches the address and the data of the fifth byte to be written. 7. the seventh bus cycle latches the address and the data of the sixth byte to be written. 8. the eighth bus cycle latches the address and the data of the seventh byte to be written. 9. the ninth bus cycle latches the address and the data of the eighth byte to be written and starts the program/erase controller. 6.2.9 unlock bypass command the unlock bypass command is used in conjunction with the unlock bypass program command to program the memory faster than with the standard program commands. when the cycle time to the device is long, considerable time saving can be made by using these commands. three bus write operations are required to issue the unlock bypass command. once the unlock bypass command has been issued the bank enters unlock bypass mode. when in unlock bypass mode, only the unlock bypass program and unlock bypass reset commands are valid. the unlock bypass program command can then be issued to program addresses within the bank, or the unlock bypass reset command can be issued to return the bank to read mode. in unlock bypass mode the memory can be read as if in read mode.
6 command interface m29dw128f 36/93 6.2.10 unlock bypass program command the unlock bypass program command can be used to program one address in the memory array at a time. the command requires two bus write operations, the final write operation latches the address and data and starts the program/erase controller. the program operation using the unlock bypass program command behaves identically to the program operation using the program command. the operation cannot be aborted, a bus read operation to the bank where the command was issued outputs the status register. see the program command for details on the behavior. 6.2.11 unlock bypass reset command the unlock bypass reset command can be used to return to read/reset mode from unlock bypass mode. two bus write operations are required to issue the unlock bypass reset command. read/reset command does not exit from unlock bypass mode. table 13. fast program commands, 8-bit mode command length bus write operations (1) 1. x don?t care, pa program address, pd program data, ba any address in the block, bka bank address, wbl write buffer location. all values in the table are in hexadecimal. 1st 2nd 3rd 4th 5th 6th 7th 8th 9th add data add data add data add data add data add data add data add data add data write to buffer and program n + 5 aaa aa 555 55 ba 25 ba n (2) 2. the maximum number of cycles in the command sequence is 37. n+1 is the number of words to be programmed during the write to b uffer and program operation. pa (3) 3. each buffer has the same a5-a22 addresses. a0-a4 are used to select a word within the n+1 word page. pd wbl (4) 4. the 6th cycle has to be issued n time. wbl scans the word inside the page. pd write to buffer and program abort and reset 3 aaa aa 555 55 aaa f0 write to buffer and program confirm 1 ba (5) 5. ba must be identical to the address loaded during the write to buffer and program 3rd and 4th cycles. 29 double byte program 3 aaa 50 pa0 pd0 pa1 pd1 quadruple byte program 5 aaa 56 pa0 pd0 pa1 pd1 pa2 pd2 pa3 pd3 octuple byte program 9 aaa 8b pa0 pd0 pa1 pd1 pa2 pd2 pa3 pd3 pa4 pd4 pa5 pd5 pa6 pd6 pa7 pd7 unlock bypass 3 aaa aa 555 55 aaa 20 unlock bypass program 2 x a0 pa pd unlock bypass reset 2x 90 x 00
m29dw128f 6 command interface 37/93 table 14. fast program commands, 16-bit mode 6.3 block protection commands blocks or groups of blocks can be protected against accidental program, erase or read operations. the protection groups are shown in appendix a , table 34: block addresses and protection groups . the device block protection scheme is shown in figure 7: software protection scheme and figure 6: block protection state diagram . see either ta b l e 1 5 , or ta b l e 1 6 , depending on the configuration that is being used, for a summary of the block protection commands. only the commands related to the extended block protection are available in both 8 bit and 16 bit memory configuration. the other block protection commands are available in 16-bit configuration only. 6.3.1 enter extended block command the m29dw128f has one extra 256-byte block (extended block) that can only be accessed using the enter extended block command. three bus write cycles are required to issue the extended block command. once the command has been issued the device enters the extended block mode where all bus read or program operations are conducted on the extended block. once the device is in the extended block mode, the extended block is addressed by using the addresses occupied by the boot blocks in the other operating modes (see table 34: block addresses and protection groups ). the device remains in extended block mode until the exit extended block command is issued or power is removed from the device. after power-up or a hardware reset, the device reverts to command length bus write operations (1) 1. x don?t care, pa program address, pd program data, ba any address in the block, bka bank address, wbl write buffer location. all values in the table are in hexadecimal. 1st 2nd 3rd 4th 5th 6th add data add data add data add data add data add data write to buffer and program n+ 5 555 aa 2aa 55 ba 25 ba n (2) 2. the maximum number of cycles in the command sequence is 37. n+1 is the number of words to be programmed during the write to buffer and program operation. pa (3) 3. each buffer has the same a5-a22 addresses. a0-a4 are used to select a word within the n+1 word page. pd wbl (4) 4. the 6th cycle has to be issued n time. wbl scans the word inside the page. pd write to buffer and program abort and reset 3 555 aa 2aa 55 555 f0 write to buffer and program confirm 1 ba (5) 5. ba must be identical to the address loaded during the write to buffer and program 3rd and 4th cycles. 29 double word program 3 555 50 pa0 pd0 pa1 pd1 quadruple word program 5 555 56 pa0 pd0 pa1 pd1 pa2 pd2 pa3 pd3 unlock bypass 3 555 aa 2aa 55 555 20 unlock bypass program 2 x a0 pa pd unlock bypass reset 2 x 90 x 00
6 command interface m29dw128f 38/93 the read mode where commands issued to the boot block address space will address the boot blocks. note that when the device is in the extended block mode, the v pp /wp pin cannot be used for fast programming and the unlock bypass mode is not available. the extended block cannot be erased, and can be treated as one-time programmable (otp) memory. in extended block mode only array cell locations (bank a) with the same addresses as the extended block are not accessible. in extended block mode dual operations are allowed and the extended block physically belongs to bank a. in extended block mode, erase, chip erase, erase suspend and erase resume commands are not allowed. to exit from the extended block mode the exit extended block command must be issued. the extended block can be protected by setting the extended block protection bit to ?1?; however once protected the protection cannot be undone. 6.3.2 exit extended block command the exit extended block command is used to exit from the extended block mode and return the device to read mode. four bus write operations are required to issue the command. 6.3.3 set extende d block protection bit command the set extended block protection bit command programs the extended block protection bit to ?1? thus preventing the second section of the extended block from being programmed. a read/reset command must be issued to abort a set extended block protection bit command. six successive steps are required to issue the set extended block protection bit command. 1. the command starts with two unlock cycles. 2. the third bus write cycle sets up the set extended block protection bit command. 3. the fourth bus write cycle programs the extended block protection bit to ?1?. 4. the last two cycles verify the value programmed at the extended block protection bit address: if bit dq0 of data inputs/outputs is set to ?1?, it indicates that the extended block protection bit has been successfully programmed. if dq0 is ?0?, the set extended block protection bit command must be issued and verified again. 6.3.4 verify extended bloc k protection bit command the verify extended block protection bit command reads the status of the extended block protection bit on bit dq0 of the data inputs/outputs. if dq0 is ?1?, the second section of the extended block is protected from program operations. 6.3.5 password program command the password program command is used to program the 64-bit password used in password protection mode. four cycles are required to program the password: 1. the first two cycles are unlock cycles. 2. the third cycle issues the password program command.
m29dw128f 6 command interface 39/93 3. the fourth cycle inputs the 16-bit data required to program the password. to program the 64-bit password, the complete command sequence must be entered four times at four consecutive addresses selected by a1 to a0. read operations can be used to read the status register during a password program operation. all other operations are forbidden. the password can be checked by issuing a password verify command. once password program operation has completed, a read/ reset command must be issued to return the device to read mode. the password protection mode can then be selected. by default, all password bits are set to ?1?. 6.3.6 password verify command the password verify command is used to verify the password used in password protection mode. to verify the 64-bit password, the complete command sequence must be entered four times at four consecutive addresses selected by a1 to a0. if the password mode locking bit is programmed and the user attempts to verify the password, the device will output all f?s onto the i/o data bus. the password is output regardless of the bank address. the user must issue a read/reset command to return the device to read mode. dual operations are not allowed during a password verify operation. 6.3.7 password protection unlock command the password protection unlock command is used to clear the lock-down bit in order to unprotect all non-volatile modify protection bits when the device is in password protection mode. the password protection unlock command must be issued along with the correct password. the complete command sequence must be entered for each 16 bits of the password. there must be a 2s delay between successive password protection unlock commands in order to prevent hackers from cracking the password by trying all possible 64-bit combinations. if this delay is not respected, the latest command will be ignored. 6.3.8 set password protection mode command the set password protection mode command puts the device in password protection mode by programming the password protection mode lock bit to ?1?. this command can be issued either with the reset/block temporary unprotect pin, rp , at v id or at v ih . six cycles are required to issue a set password protection mode command: 1. the first two cycles are unlock cycles. 2. the third cycle issues the command. 3. the fourth and fifth cycles select the address (see table 17: protection command addresses ). 4. the last cycle verifies if the operation has been successful. if dq0 is set to ?1?, the device has successfully entered the password protection mode. if dq0 is ?0?, the operation has failed and the command must be re-issued. there must be a 100s delay between the fourth and fifth cycles.
6 command interface m29dw128f 40/93 once the password protection mode is activated the device will permanently remain in this mode. 6.3.9 verify password protection mode command the verify password protection mode command reads the status of the password protection mode lock bit. if it is ?1?, the device is in password protection mode. 6.3.10 set standard protection mode command the set standard protection mode command puts the device in standard protection mode by programming the standard protection mode lock bit to ?1?. six cycles are required to issue the standard protection mode command: 1. the first two cycles are unlock cycles. 2. the third cycle issues the program command. 3. the fourth and fifth cycles select the address (see table 17: protection command addresses ). 4. the last cycle verifies if the operation has been successful. if dq0 is set to ?1?, the standard protection mode has been successfully activated. if dq0 is ?0?, the operation has failed and the command must be re-issued. there must be a 100s delay between the fourth and fifth cycles. once the standard protection mode is activated the device will permanently remain in this mode. 6.3.11 verify standard protection mode command the verify standard protection mode command reads the status of the standard protection mode lock bit. if it is ?1?, the device is in standard protection mode. 6.3.12 set non-volatile m odify protection bit command a block or group of blocks can be protected from program or erase by issuing a set non-volatile modify protection bit command along with the block address. this command sets the non- volatile modify protection bit to ?1? for a given block or group of blocks. six cycles are required to issue the command: 1. the first two cycles are unlock cycles. 2. the third cycle issues the program command. 3. the fourth and fifth cycles select the address (see table 17: protection command addresses ). 4. the last cycle verifies if the operation has been successful. if dq0 is set to ?1?, the non- volatile modify protection bit has been successfully programmed. if dq0 is ?0?, the operation has failed and the command must be re-issued. there must be a 100s delay between the fourth and fifth cycles. the non-volatile modify protection bits are erased simultaneously by issuing a clear non- volatile modify protection bits command except if the lock-down bit is set to ?1?. the non-volatile modify protection bits can be set a maximum of 100 times.
m29dw128f 6 command interface 41/93 6.3.13 verify non-volatile modify protection bit command the status of a non-volatile modify protection bit for a given block or group of blocks can be read by issuing a verify non-volatile modify protection bit command along with the block address. 6.3.14 clear non-volatile m odify protection bits command this command is used to clear all non-volatile modify protection bits. no specific block address is required. if the lock-down bit is set to ?1?, the command will fail. six cycles are required to issue a clear non-volatile modify protection bits command: 1. the first two cycles are unlock cycles. 2. the third cycle issues the command. 3. the last three cycles verify if the operation has been successful. if dq0 is set to ?0?, all non-volatile modify protection bits have been successfully cleared. if dq0 is ?1?, the operation has failed and the command must be re-issued. there must be a 12ms delay between the fourth and fifth cycles. 6.3.15 set lock bit command the set lock bit command individually sets the lock bit to ?1? for a given block or group of blocks. if the non-volatile lock bit for the same block or group of blocks is set, the block is locked regardless of the value of the lock bit. (see table 10: block protection status ). 6.3.16 clear lock bit command the clear lock bit command individually clears (sets to ?0?) the lock bit for a given block or group of blocks. if the non-volatile lock bit for the same block or group of blocks is set, the block or group of blocks remains locked (see table 10: block protection status ). 6.3.17 verify lock bit command the status of a lock bit for a given block can be read by issuing a verify lock bit command along with the block address. 6.3.18 set lock-down bit command this command is used to set the lock-down bit to ?1? thus protecting the non-volatile modify protection bits from program and erase. there is no unprotect lock-down bit command. 6.3.19 verify lock-down bit command this command is used to read the status of the lock-down bit. the status is output on bit dq1. if dq1 is ?1?, all the non-volatile modify protection bits are protected from program or erase operations.
6 command interface m29dw128f 42/93 table 15. block protection commands, 8-bit mode table 16. block protection commands, 16-bit mode command length bus operations (1)(2) 1. ow extended block protection bit address (a7-a0=?00011010?), x don?t care. all values in the table are in hexadecimal. 2. grey cells represent read cycles . the other cells are write cycles. 1st 2nd 3rd 4th 5th 6th add data add data add data add data add data add data set extended block protection bit 6 aaa aa 555 55 aaa 60 ow 68 ow (3) 3. a 100s timeout is required between cycles 4 and 5. 48 ow dq0 verify extended block protection bit 4 aaa aa 555 55 aaa 60 ow dq0 enter extended block 3 aaa aa 555 55 aaa 88 exit extended block 4 aaa aa 555 55 aaa 90 x 00 command length bus operations (1)(2)(3)(4) 1st 2nd 3rd 4th 5th 6th 7th add data add data add data add data add data add data add data set extended block protection bit (5)(6) 6 555 aa 2aa 55 555 60 ow 68 ow 48 ow dq0 verify extended block protection bit 4 555 aa 2aa 55 555 60 ow dq0 enter extended block 3 555 aa 2aa 55 555 88 exit extended block 4 555 aa 2aa 55 555 90 x 00 password program (5)(7)(8) 4 555 aa 2aa 55 555 38 x[0-3] pw [0-3] password verify (8)(9) 4 555 aa 2aa 55 555 c8 pwa [0-3] rpw [0-3] password protection unlock (7)(10)(11) 7 555 aa 2aa 55 555 28 pwa [0] rpw [0] pwa [1] rpw [1] pwa [2] rpw [2] pwa [3] rpw [3] set password protection mode (5)(6) 6 555 aa 2aa 55 555 60 pl 68 pl 48 pl dq0 verify password protection mode 4 555 aa 2aa 55 555 60 pl dq0
m29dw128f 6 command interface 43/93 set non- volatile modify protection bit (5) (6) 6 555 aa 2aa 55 555 60 (ba)/ nvmp 68 (ba)/ nvmp 48 (ba)/ nvmp dq0 verify non- volatile modify protection bit 4 555 aa 2aa 55 555 60 (ba) / nvmp 48 (ba)/ nvmp dq0 clear non- volatile modify protection bits (12)(13)(14) 6 555 aa 2aa 55 555 60 nvmp 60 (ba)/ nvmp 40 (ba)/ nvmp dq0 set lock-down bit 3 555 aa 2aa 55 555 78 verify lock- down bit (15) 4 555 aa 2aa 55 555 58 ba dq1 set lock bit (7) 4 555 aa 2aa 55 555 48 ba x1h clear lock bit (7) 4 555 aa 2aa 55 555 48 ba x0h verify lock bit 4 555 aa 2aa 55 555 58 ba dq0 set standard protection mode (5)(6) 6 555 aa 2aa 55 555 60 sl 68 sl 48 sl dq0 verify standard protection mode (5) 4 555 aa 2aa 55 555 60 sl dq0 1. grey cells represent read cycles . the other cells are write cycles. 2. sa protection group address, ba any address in the block, bka bank address, sl standard protection mode lock bit address, pl password protection mode lock bit address, pw password data, pwa password address, rpw password data being verified, nvmp non-volatile modify protection bit address, ow extended block protection bit address, x don?t care. all values in the table are in hexadecimal. 3. addresses are described in table 17: protection command addresses . 4. during unlock and command cycles, if the lower address bits are 555h or 2aah then the address bits higher than a11 (except where ba is required) and data bits higher than dq7 are don't care. 5. a reset command must be issued to return to the read mode. 6. the 4 th bus write cycle programs a protection bit (extended block protection bit, password protection mode lock bit, standard protection mode lock bit, and a block nvmp bit). the 5 th and 6 th cycles verify that the bit has been successively programmed when dq0=1. if dq0=0 in the 6 th cycle, the program command must be issued again and verified again. a 100s delay is required between the 4th and the 5th cycle. 7. data is latched on the rising edge of w . 8. the entire command sequence must be entered for each portion of the password. 9. the command sequence returns ffh if the password protection mode locking bit is set. 10. the password is written over four consecutive cycles, at addresses [0-3] 11. a 2s timeout is required between any two portions of the password. 12. a 10ms delay is required between the 4th and the 5th cycle. 13. a 12ms timeout is requir ed between cycles 4 and 5. command length bus operations (1)(2)(3)(4) 1st 2nd 3rd 4th 5th 6th 7th add data add data add data add data add data add data add data
6 command interface m29dw128f 44/93 table 17. protection command addresses table 18. program, erase times and program, erase endurance cycles 14. cycle 4 erases all non-volatile modify protection bits. cycles 5 and 6 verify that the bits have been successfully cleared when dq0=0. if dq0=1 in the 6 th cycle, the erase command must be issued again and verified again. before issuing the erase command, all non-volatile modify protection bits should be programmed to prevent over erasure. 15. dq1=1 if the non-volatile modify protection bit is locked, dq1 = 0 if it is unlocked. bit condition address inputs a7-a0 other address inputs password protection mode lock bit address (pl) rp at v ih 00001010 x rp at v id 10001010 x standard protection mode lock bit address (sl) 00010010 x non-volatile modify protection bit address (nvmp) 01000010 block protection group address extended block protection bit address (ow) 00011010 x parameter min typ (1)(2) 1. typical values measured at room temperature and nominal voltages. 2. sampled, but not 100% tested. max (2) unit chip erase 80 400 (3) 3. maximum value measured at worst case conditions for both temperature and v cc after 100,00 program/erase cycles. s block erase (64 kbytes) 0.8 6 (4) 4. maximum value measured at worst case conditions for both temperature and v cc . s erase suspend latency time 50 (4) s byte program single or multiple byte program (1, 2, 4 or 8 bytes at-a-time) 10 200 (3) s write to buffer and program (64 bytes at-a-time) v pp /wp =v pph 90 s v pp /wp =v ih 280 word program single or multiple word program (1, 2 or 4 words at-a-time) 10 200 (3) s write to buffer and program (32 words at-a-time) v pp /wp = v pph 90 s v pp /wp =v ih 280 chip program (byte by byte) 80 400 (3) s chip program (word by word) 40 200 (3) s chip program (quadruple byte or double word) 20 100 (3) s chip program (octuple byte or quadruple word) 10 50 (3) s program suspend latency time 4 s program/erase cycles (per block) 100,000 cycles data retention 20 years
m29dw128f 7 status register 45/93 7 status register the m29dw128f has one status register. the status register provides information on the current or previous program or erase operations executed in each bank. the various bits convey information and errors on the operation. bus read operations from any address within the bank, always read the status register during program and erase operations. it is also read during erase suspend when an address within a block being erased is accessed. the bits in the status register are summarized in table 19: status register bits . 7.1 data polling bit (dq7) the data polling bit can be used to identify whether the program/erase controller has successfully completed its operation or if it has responded to an erase suspend. the data polling bit is output on dq7 when the status register is read. during program operations the data polling bit outputs the complement of the bit being programmed to dq7. after successful completion of the program operation the memory returns to read mode and bus read operations from the address just programmed output dq7, not its complement. during erase operations the data polling bit outputs ?0?, the complement of the erased state of dq7. after successful completion of the erase operation the memory returns to read mode. in erase suspend mode the data polling bit will output a ?1? during a bus read operation within a block being erased. the data polling bit will change from a ?0? to a ?1? when the program/ erase controller has suspended the erase operation. figure 8: data polling flowchart , gives an example of how to use the data polling bit. a valid address is the address being programmed or an address within the block being erased. 7.2 toggle bit (dq6) the toggle bit can be used to identify whether the program/erase controller has successfully completed its operation or if it has responded to an erase suspend. the toggle bit is output on dq6 when the status register is read. during a program/erase operation the toggle bit changes from ?0? to ?1? to ?0?, etc., with successive bus read operations at any address. after successful completion of the operation the memory returns to read mode. during erase suspend mode the toggle bit will output when addressing a cell within a block being erased. the toggle bit will stop toggling when the program/erase controller has suspended the erase operation. figure 9: toggle flowchart , gives an example of how to use the data toggle bit. figure 16 and figure 17 describe toggle bit timing waveform.
7 status register m29dw128f 46/93 7.3 error bit (dq5) the error bit can be used to identify errors detected by the program/erase controller. the error bit is set to ?1? when a program, block erase or chip erase operation fails to write the correct data to the memory. if the error bit is set a read/reset command must be issued before other commands are issued. the error bit is output on dq5 when the status register is read. note that the program command cannot change a bit set to ?0? back to ?1? and attempting to do so will set dq5 to ?1?. a bus read operation to that address will show the bit is still ?0?. one of the erase commands must be used to set all the bits in a block or in the whole memory from ?0? to ?1?. 7.4 erase timer bit (dq3) the erase timer bit can be used to identify the start of program/erase controller operation during a block erase command. once the program/erase controller starts erasing the erase timer bit is set to ?1?. before the program/erase controller starts the erase timer bit is set to ?0? and additional blocks to be erased may be written to the command interface. the erase timer bit is output on dq3 when the status register is read. 7.5 alternative toggle bit (dq2) the alternative toggle bit can be used to monitor the program/erase controller during erase operations. the alternative toggle bit is output on dq2 when the status register is read. during chip erase and block erase operations the toggle bit changes from ?0? to ?1? to ?0?, etc., with successive bus read operations from addresses within the blocks being erased. a protected block is treated the same as a block not being erased. once the operation completes the memory returns to read mode. during erase suspend the alternative toggle bit changes from ?0? to ?1? to ?0?, etc. with successive bus read operations from addresses within the blocks being erased. bus read operations to addresses within blocks not being erased will output the memory array data as if in read mode. after an erase operation that causes the error bit to be set, the alternative toggle bit can be used to identify which block or blocks have caused the error. the alternative toggle bit changes from ?0? to ?1? to ?0?, etc. with successive bus read operations from addresses within blocks that have not erased correctly. the alternative toggle bit does not change if the addressed block has erased correctly. figure 16 and figure 17 describe alternative toggle bit timing waveform. 7.6 write to buffer and program abort bit (dq1) the write to buffer and program abort bit, dq1, is set to ?1? when a write to buffer and program operation aborts. the write to buffer and program abort and reset command must be issued to return the device to read mode (see write to buffer and program in commands section).
m29dw128f 7 status register 47/93 table 19. status register bits 1. unspecified data bits should be ignored. 2. figure 16 and figure 17 describe toggle and alternative toggle bits timing waveforms. figure 8. data polling flowchart operation address dq7 dq6 dq5 dq3 dq2 dq1 rb program bank address dq7 toggle 0 ? ? 0 0 program during erase suspend bank address dq7 toggle 0 ? ? ? 0 write to buffer and program abort bank address dq7 toggle 0 ? ? 1 0 program error bank address dq7 toggle 1 ? ? ? hi-z chip erase any address 0 toggle 0 1 toggle ? hi-z block erase before timeout erasing block 0 toggle 0 0 toggle ? 0 non-erasing block 0 toggle 0 0 no toggle ? 0 block erase erasing block 0 toggle 0 1 toggle ? hi-z non-erasing block 0 toggle 0 1 no toggle ? 0 erase suspend erasing block 1 no toggle 0 ? toggle ? hi-z non-erasing block data read as normal ? hi-z erase error good block address 0 toggle 1 1 no toggle ? 0 faulty block address 0 toggle 1 1 toggle ? 0 read dq5 & dq7 at valid address start read dq7 at valid address fail pass ai07760 dq7 = data yes no yes no dq5 = 1 dq7 = data yes no
7 status register m29dw128f 48/93 figure 9. toggle flowchart 1. ba = address of bank being programmed or erased. read dq6 address = ba start read dq6 twice address = ba fail pass ai08929b dq6 = toggle no no yes yes dq5 = 1 no yes dq6 = toggle read dq5 & dq6 address = ba
m29dw128f 8 dual operations and multiple bank architecture 49/93 8 dual operations and multiple bank architecture the multiple bank architecture of the m29dw128f gives greater flexibility for software developers to split the code and data spaces within the memory array. the dual operations feature simplifies the software management of the device by allowing code to be executed from one bank while another bank is being programmed or erased. the dual operations feature means that while programming or erasing in one bank, read operations are possible in another bank with zero latency. only one bank at a time is allowed to be in program or erase mode. however, certain commands can cross bank boundaries, which means that during an operation only the banks that are not concerned with the cross bank operation are available for dual operations. for example, if a block erase command is issued to erase blocks in both bank a and bank b, then only banks c or d are available for read operations while the erase is being executed. if a read operation is required in a bank, which is programming or erasing, the program or erase operation can be suspended. also if the suspended operation was erase then a program command can be issued to another block, so the device can have one block in erase suspend mode, one programming and other banks in read mode. by using a combination of these features, read operations are possible at any moment. ta b l e 2 0 and ta bl e 2 1 show the dual operations possible in other banks and in the same bank. note that only the commonly used commands are represented in these tables. table 20. dual operations allowed in other banks status of bank commands allowed in another bank (1) 1. if several banks are involved in a program or erase operation, then only the banks that are not concerned with the operation are available for dual operations. read/ reset read status register (2) 2. read status register is not a command. the status register can be read during a block program or erase operation. read cfi query auto select program erase program/ erase suspend program /erase resume idle yes ye s (3) ye s ye s ye s ye s ye s (3) 3. only after a program or erase operation in that bank. ye s (4) 4. only after a program or erase suspend command in that bank. programming yes no no no ? ? no no erasing yes no no no ? ? no no program suspended ye s n o ye s ye s n o n o - ye s (5) 5. only a program resume is allowed if t he bank was previously in program suspend mode. erase suspended yes no yes yes yes no - ye s (6) 6. only an erase resume is allowed if t he bank was previously in erase suspend mode.
8 dual operations and multiple bank architecture m29dw128f 50/93 table 21. dual operations allowed in same bank status of bank commands allowed in same bank read/ reset read status register (1) 1. read status register is not a command. the stat us register can be read by addressing the block being programmed or erased. read cfi query auto select program erase program/ erase suspend program/ erase resume idle yes yes yes yes yes yes ye s (2) 2. only after a program or erase operation in that bank. ye s (3) 3. only after a program or erase suspend command in that bank. programming no yes no no ? ? ye s (4) 4. only a program suspend. ? erasing no yes no no ? no ye s (5) 5. only an erase suspend. ? program suspended ye s (6) 6. not allowed in the block or word that is being erased or programmed. no yes yes no ? ? yes erase suspended ye s (6) ye s (7) 7. the status register can be read by addressing the block being erase suspended. ye s ye s ye s (6) no ? yes
m29dw128f 9 maximum rating 51/93 9 maximum rating stressing the device above the rating listed in the absolute maximum ratings table may cause permanent damage to the device. exposure to absolute maximum rating conditions for extended periods may affect device reliability. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not implied. refer also to the stmicroelectronics sure program and other relevant quality documents. table 22. absolute maximum ratings symbol parameter min max unit t bias temperature under bias ?50 125 c t stg storage temperature ?65 150 c v io input or output voltage (1)(2) 1. minimum voltage may undershoot to ?2v during transition and for less than 20ns during transitions. 2. maximum voltage may overshoot to v cc +2v during transition and for less than 20ns during transitions. ?0.6 v cc +0.6 v v cc supply voltage ?0.6 4 v v ccq input/output supply voltage ?0.6 4 v v id identification voltage ?0.6 13.5 v v pp (3) 3. v pp must not remain at 12v for more than a total of 80hrs. program voltage ?0.6 13.5 v
10 dc and ac parameters m29dw128f 52/93 10 dc and ac parameters this section summarizes the operating measurement conditions, and the dc and ac characteristics of the device. the parameters in the dc and ac characteristics tables that follow, are derived from tests performed under the measurement conditions summarized in table 23: operating and ac measurement conditions . designers should check that the operating conditions in their circuit match the operating conditions when relying on the quoted parameters. table 23. operating and ac measurement conditions figure 10. ac measurement i/o waveform figure 11. ac measurement load circuit parameter m29dw128f unit 60 70 min max min max v cc supply voltage 2.7 3.6 2.7 3.6 v ambient operating temperature ?40 85 ?40 85 c load capacitance (c l ) 30 30 pf input rise and fall times 10 10 ns input pulse voltages 0 to v cc 0 to v cc v input and output timing ref. voltages v cc /2 v cc /2 v ai05557 v cc 0v v cc /2 ai05558 c l c l includes jig capacitance device under test 25k ? v cc 25k ? v cc 0.1f v pp 0.1f
m29dw128f 10 dc and ac parameters 53/93 table 24. device capacitance table 25. dc characteristics symbol parameter test condition min max (1) 1. sampled only, not 100% tested. unit c in input capacitance v in = 0v 6pf c out output capacitance v out = 0v 12 pf symbol parameter test condition min max unit i li input leakage current 0v v in v cc 1 a i lo output leakage current 0v v out v cc 1 a i cc1 (1) 1. in dual operations the supply current will be the sum of i cc1 (read) and i cc3 (program/erase). supply current (read) e = v il , g = v ih , f = 6mhz 10 ma i cc2 supply current (standby) e = v cc 0.2v, rp = v cc 0.2v 100 a i cc3 (1)(2) 2. sampled only, not 100% tested. supply current (program/ erase) program/erase controller active v pp /wp = v il or v ih 20 ma v pp /wp = v pph 20 ma v il input low voltage ?0.5 0.8 v v ih input high voltage 0.7v cc v cc +0.3 v v pph voltage for v pp /wp program acceleration v cc = 2.7v 10% 11.5 12.5 v i pp current for v pp /wp program acceleration v cc =2.7v 10% 15 ma v ol output low voltage i ol = 1.8ma 0.45 v v oh output high voltage i oh = ?100 av cc ?0.4 v v id identification voltage 11.5 12.5 v v lko program/erase lockout supply voltage 1.8 2.3 v
10 dc and ac parameters m29dw128f 54/93 figure 12. random read ac waveforms ai08970 tavav tavqv taxqx telqx tehqz tglqv tglqx tghqx valid a0-a22/ a?1 g dq0-dq7/ dq8-dq15 e telqv tehqx tghqz valid tbhqv telbl/telbh tblqz byte
m29dw128f 10 dc and ac parameters 55/93 figure 13. page read ac waveforms ai08971c tehqz tghqx valid a3-a22 a-1 g dq0-dq15 e telqv tehqx tghqz valid a0-a2 valid valid valid valid valid valid valid tglqv tavqv tavqv1 valid valid valid valid valid valid valid valid
10 dc and ac parameters m29dw128f 56/93 table 26. read ac characteristics symbol alt parameter test condition m29dw128f unit 60 70 t avav t rc address valid to next address valid e = v il , g = v il min 60 70 ns t avqv t acc address valid to output valid e = v il , g = v il max 60 70 ns t avqv1 t pag e address valid to output valid (page) e = v il , g = v il max 25 30 ns t elqx (1) 1. sampled only, not 100% tested. t lz chip enable low to output transition g = v il min 0 0 ns t elqv t ce chip enable low to output valid g = v il max 60 70 ns t glqx (1) t olz output enable low to output transition e = v il min 0 0 ns t glqv t oe output enable low to output valid e = v il max 20 25 ns t ehqz (1) t hz chip enable high to output hi-z g = v il max 25 25 ns t ghqz (1) t df output enable high to output hi-z e = v il max 25 25 ns t ehqx t ghqx t axqx t oh chip enable, output enable or address transition to output transition min 0 0 ns t elbl t elbh t elfl t elfh chip enable to byte low or high (2) 2. tsop56 package only. max 5 5 ns t blqz t flqz byte low to output hi-z (2) max 25 25 ns t bhqv t fhqv byte high to output valid (2) max 30 30 ns
m29dw128f 10 dc and ac parameters 57/93 figure 14. write ac waveforms, write enable controlled ai08972 e g w a0-a22/ a?1 dq0-dq7/ dq8-dq15 valid valid v cc tvchel twheh twhwl telwl tavwl twhgl twlax twhdx tavav tdvwh twlwh tghwl rb twhrl
10 dc and ac parameters m29dw128f 58/93 table 27. write ac characteristics, write enable controlled symbol alt parameter m29dw128f unit 60 70 t avav t wc address valid to next address valid min 60 70 ns t elwl t cs chip enable low to write enable low min 0 0 ns t wlwh t wp write enable low to write enable high min 45 45 ns t dvwh t ds input valid to write enable high min 45 45 ns t whdx t dh write enable high to input transition min 0 0 ns t wheh t ch write enable high to chip enable high min 0 0 ns t whwl t wph write enable high to write enable low min 30 30 ns t avwl t as address valid to write enable low min 0 0 ns t wlax t ah write enable low to address transition min 45 45 ns t ghwl output enable high to write enable low min 0 0 ns t whgl t oeh write enable high to output enable low min 0 0 ns t whrl (1) 1. sampled only, not 100% tested. t busy program/erase valid to rb low max 30 30 ns t vchel t vcs v cc high to chip enable low min 50 50 s
m29dw128f 10 dc and ac parameters 59/93 figure 15. write ac waveforms, chip enable controlled ai0897 3 e g w a0-a22/ a?1 dq0-dq7/ dq8-dq15 valid valid v cc tvchwl tehwh tehel twlel tavel tehgl telax tehdx tavav tdveh teleh tghel rb tehrl
10 dc and ac parameters m29dw128f 60/93 table 28. write ac characteristics, chip enable controlled symbol alt parameter m29dw128f unit 60 70 t avav t wc address valid to next address valid min 60 70 ns t wlel t ws write enable low to chip enable low min 0 0 ns t eleh t cp chip enable low to chip enable high min 45 45 ns t dveh t ds input valid to chip enable high min 45 45 ns t ehdx t dh chip enable high to input transition min 0 0 ns t ehwh t wh chip enable high to write enable high min 0 0 ns t ehel t cph chip enable high to chip enable low min 30 30 ns t avel t as address valid to chip enable low min 0 0 ns t elax t ah chip enable low to address transition min 45 45 ns t ghel output enable high chip enable low min 0 0 ns t ehgl t oeh chip enable high to output enable low min 0 0 ns t ehrl (1) 1. sampled only, not 100% tested. t busy program/erase valid to rb low max 30 30 ns t vchwl t vcs v cc high to write enable low min 50 50 s
m29dw128f 10 dc and ac parameters 61/93 figure 16. toggle and alternative toggle bits mechanism, chip enable controlled 1. the toggle bit is output on dq6. 2. the alternative toggle bit is output on dq2. 3. refer to table 26: read ac characteristics for the value of t elqv . figure 17. toggle and alternative toggle bits mechanism, output enable controlled 1. the toggle bit is output on dq6. 2. the alternative toggle bit is output on dq2. 3. refer to table 26: read ac characteristics for the value of t glqv . table 29. toggle and alternative toggle bits ac characteristics symbol alt parameter m29dw128f unit 60 70 t axel address transition to chip enable low min 10 10 ns t axgl address transition to output enable low min 10 10 ns ai08914e g a0-a22 dq2 (1) /dq6 (2) e taxel telqv data data toggle/ alt.toggle bit telqv address in the bank being programmed or erased read operation outside the bank being programmed or erased address outside the bank being programmed or erased toggle/ alt.toggle bit read operation outside the bank being programmed or erased read operation in the bank being programmed or erased address outside the bank being programmed or erased ai08915e g a0-a22 dq2 (1) /dq6 (2) e taxgl tglqv data data toggle/ alt.toggle bit tglqv address in the bank being programmed/erased read operation outside bank being programmed or erased address outside the bank being programmed/erased toggle/ alt.toggle bit read operation outside bank being programmed or erased read operation in bank being programmed or erased address outside the bank being programmed/erased
10 dc and ac parameters m29dw128f 62/93 figure 18. reset/block temporary unprotect ac waveforms (no program/erase ongoing) figure 19. reset/block temporary unprotect during program/erase operation ac waveforms table 30. reset/block temporary unprotect ac characteristics symbol alt parameter m29dw128f unit 60 70 t plyh (1) 1. sampled only, not 100% tested. t ready rp low to read mode, during program or erase max 20 s t plpx t rp rp pulse width min 500 ns t phel, t phgl (1) t rh rp high to write enable low, chip enable low, output enable low min 50 ns t rpd rp low to standby mode. min 20 ns t rhel t rhgl (1) t rb rb high to write enable low, chip enable low, output enable low min 0 ns ai11300b rb rp tplpx tphel, tphgl e, g ai11301b rb rp tplpx trhel, trhgl e, g tplyh
m29dw128f 10 dc and ac parameters 63/93 figure 20. accelerated program timing waveforms ai05563 v pp /wp v pp v il or v ih tvhvpp tvhvpp
11 package mechanical m29dw128f 64/93 11 package mechanical figure 21. tsop56 ? 56 lead plastic thin small outline, 14 x 20mm, package outline 1. drawing is not to scale. table 31. tsop56 ? 56 lead plastic thin small outline, 14 x 20mm, package mechanical data symbol millimeters inches typ min max typ min max a 1.200 0.0472 a1 0.100 0.050 0.150 0.0039 0.0020 0.0059 a2 1.000 0.950 1.050 0.0394 0.0374 0.0413 b 0.220 0.170 0.270 0.0087 0.0067 0.0106 c 0.100 0.210 0.0039 0.0083 cp 0.100 0.0039 d 20.000 19.800 20.200 0.7874 0.7795 0.7953 d1 18.400 18.300 18.500 0.7244 0.7205 0.7283 e 0.500 ? ? 0.0197 ? ? e 14.000 13.900 14.100 0.5512 0.5472 0.5551 l 0.600 0.500 0.700 0.0236 0.0197 0.0276 alpha305305 n56 56 tsop-b d1 e 1 n cp b e a2 a n/2 d die c l a1
m29dw128f 11 package mechanical 65/93 figure 22. tbga64 10x13mm - 8x8 active ball array, 1mm pitch, package outline 1. drawing is not to scale. table 32. tbga64 10x13mm - 8x8 active ball array, 1mm pitch, package mechanical data symbol millimeters inches typ min max typ min max a 1.200 0.0472 a1 0.300 0.200 0.350 0.0118 0.0079 0.0138 a2 0.800 0.0315 b 0.350 0.500 0.0138 0.0197 d 10.000 9.900 10.100 0.3937 0.3898 0.3976 d1 7.000 ? ? 0.2756 ? ? ddd 0.100 0.0039 e 1.000 ? ? 0.0394 ? ? e 13.000 12.900 13.100 0.5118 0.5079 0.5157 e1 7.000 ? ? 0.2756 ? ? fd 1.500 ? ? 0.0591 ? ? fe 3.000 ? ? 0.1181 ? ? sd 0.500 ? ? 0.0197 ? ? se 0.500 ? ? 0.0197 ? ? e1 e d1 d eb sd se a2 a1 a bga-z23 ddd fd fe ball "a1"
12 part numbering m29dw128f 66/93 12 part numbering table 33. ordering information scheme note: this product is also available with the extended block factory locked. for further details and ordering information contact your nearest st sales office. devices are shipped from the factory with the memory content bits erased to ?1?. for a list of available options (speed, package, etc.) or for further information on any aspect of this device, please contact your nearest st sales office. example: m29dw128f 70 nf 1 t device type m29 architecture d = dual operation operating voltage w = v cc = 2.7 to 3.6v device function 128f = 128 mbit (x8/x16), multiple bank, page, boot block, 16+48+48+16 partitioning, flash memory speed 60 = 60ns 70 = 70ns package nf = tsop56: 14 x 20 mm za = tbga64: 10 x13mm, 1mm pitch temperature range 1 = 0 to 70 c 6 = ?40 to 85 c option blank = standard packing t = tape & reel packing e = ecopack package, standard packing f = ecopack package, tape & reel 24mm packing
m29dw128f 12 part numbering 67/93 appendix a block addresses and read/modify protection groups table 34. block addresses and protection groups bank block size (kbytes/ kwords) protection block group (x8) (x16) bank a 0 8/4 protection group 000000h-001fffh (1) 000000h?000fffh (1) 1 8/4 protection group 002000h-003fffh (1) 001000h?001fffh (1) 2 8/4 protection group 004000h-005fffh (1) 002000h?002fffh (1) 3 8/4 protection group 006000h-007fffh (1) 003000h?003fffh (1) 4 8/4 protection group 008000h-009fffh (1) 004000h?004fffh (1) 5 8/4 protection group 00a000h-00bfffh (1) 005000h?005fffh (1) 6 8/4 protection group 00c000h-00dfffh (1) 006000h?006fffh (1) 7 8/4 protection group 00e000h-00ffffh (1) 007000h?007fffh (1) 8 64/32 protection group 010000h-01ffffh 008000h?00ffffh 9 64/32 020000h-02ffffh 010000h?017fffh 10 64/32 030000h-03ffffh 018000h?01ffffh 11 64/32 protection group 040000h-04ffffh 020000h?027fffh 12 64/32 050000h-05ffffh 028000h?02ffffh 13 64/32 060000h-06ffffh 030000h?037fffh 14 64/32 070000h-07ffffh 038000h?03ffffh 15 64/32 protection group 080000h-08ffffh 040000h?047fffh 16 64/32 090000h-09ffffh 048000h?04ffffh 17 64/32 0a0000h-0affffh 050000h?057fffh 18 64/32 0b0000h-0bffffh 058000h?05ffffh 19 64/32 protection group 0c0000h-0cffffh 060000h?067fffh 20 64/32 0d0000h-0dffffh 068000h?06ffffh 21 64/32 0e0000h-0effffh 070000h?077fffh 22 64/32 0f0000h-0fffffh 078000h?07ffffh 23 64/32 protection group 100000h-10ffffh 080000h?087fffh 24 64/32 110000h-11ffffh 088000h?08ffffh 25 64/32 120000h-12ffffh 090000h?097fffh 26 64/32 130000h-13ffffh 098000h?09ffffh
12 part numbering m29dw128f 68/93 bank a 27 64/32 protection group 140000h-14ffffh 0a0000h?0a7fffh 28 64/32 150000h-15ffffh 0a8000h?0affffh 29 64/32 160000h-16ffffh 0b0000h?0b7fffh 30 64/32 170000h-17ffffh 0b8000h?0bffffh 31 64/32 protection group 180000h-18ffffh 0c0000h?0c7fffh 32 64/32 190000h-19ffffh 0c8000h?0cffffh 33 64/32 1a0000h-1affffh 0d0000h?0d7fffh 34 64/32 1b0000h-1bffffh 0d8000h?0dffffh 35 64/32 protection group 1c0000h-1cffffh 0e0000h?0e7fffh 36 64/32 1d0000h-1dffffh 0e8000h?0effffh 37 64/32 1e0000h-1effffh 0f0000h?0f7fffh 38 64/32 1f0000h-1fffffh 0f8000h?0fffffh bank b 39 64/32 protection group 200000h-20ffffh 100000h?107fffh 40 64/32 210000h-21ffffh 108000h?10ffffh 41 64/32 220000h-22ffffh 110000h?117fffh 42 64/32 230000h-23ffffh 118000h?11ffffh 43 64/32 protection group 240000h-24ffffh 120000h?127fffh 44 64/32 250000h-25ffffh 128000h?12ffffh 45 64/32 260000h-26ffffh 130000h?137fffh 46 64/32 270000h-27ffffh 138000h?13ffffh 47 64/32 protection group 280000h-28ffffh 140000h?147fffh 48 64/32 290000h-29ffffh 148000h?14ffffh 49 64/32 2a0000h-2affffh 150000h?157fffh 50 64/32 2b0000h-2bffffh 158000h?15ffffh 51 64/32 protection group 2c0000h-2cffffh 160000h?167fffh 52 64/32 2d0000h-2dffffh 168000h?16ffffh 53 64/32 2e0000h-2effffh 170000h?177fffh 54 64/32 2f0000h-2fffffh 178000h?17ffffh 55 64/32 protection group 300000h-30ffffh 180000h?187fffh 56 64/32 310000h-31ffffh 188000h?18ffffh 57 64/32 320000h-32ffffh 190000h?197fffh 58 64/32 330000h-33ffffh 198000h?19ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
m29dw128f 12 part numbering 69/93 bank b 59 64/32 protection group 340000h-34ffffh 1a0000h?1a7fffh 60 64/32 350000h-35ffffh 1a8000h?1affffh 61 64/32 360000h-36ffffh 1b0000h?1b7fffh 62 64/32 370000h-37ffffh 1b8000h?1bffffh 63 64/32 protection group 380000h-38ffffh 1c0000h?1c7fffh 64 64/32 390000h-39ffffh 1c8000h?1cffffh 65 64/32 3a0000h-3affffh 1d0000h?1d7fffh 66 64/32 3b0000h-3bffffh 1d8000h?1dffffh 67 64/32 protection group 3c0000h-3cffffh 1e0000h?1e7fffh 68 64/32 3d0000h-3dffffh 1e8000h?1effffh 69 64/32 3e0000h-3effffh 1f0000h?1f7fffh 70 64/32 3f0000h-3fffffh 1f8000h?1fffffh 71 64/32 protection group 400000h?40ffffh 200000h?207fffh 72 64/32 410000h?41ffffh 208000h?20ffffh 73 64/32 420000h?42ffffh 210000h?217fffh 74 64/32 430000h?43ffffh 218000h?21ffffh 75 64/32 protection group 440000h?44ffffh 220000h?227fffh 76 64/32 450000h?45ffffh 228000h?22ffffh 77 64/32 460000h?46ffffh 230000h?237fffh 78 64/32 470000h?47ffffh 238000h?23ffffh 79 64/32 protection group 480000h?48ffffh 240000h?247fffh 80 64/32 490000h?49ffffh 248000h?24ffffh 81 64/32 4a0000h?4affffh 250000h?257fffh 82 64/32 4b0000h?4bffffh 258000h?25ffffh 83 64/32 protection group 4c0000h?4cffffh 260000h?267fffh 84 64/32 4d0000h?4dffffh 268000h?26ffffh 85 64/32 4e0000h?4effffh 270000h?277fffh 86 64/32 4f0000h?4fffffh 278000h?27ffffh 87 64/32 protection group 500000h?50ffffh 280000h?287fffh 88 64/32 510000h?51ffffh 288000h?28ffffh 89 64/32 520000h?52ffffh 290000h?297fffh 90 64/32 530000h?53ffffh 298000h?29ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
12 part numbering m29dw128f 70/93 bank b 91 64/32 protection group 540000h?54ffffh 2a0000h?2a7fffh 92 64/32 550000h?55ffffh 2a8000h?2affffh 93 64/32 560000h?56ffffh 2b0000h?2b7fffh 94 64/32 570000h?57ffffh 2b8000h?2bffffh 95 64/32 protection group 580000h?58ffffh 2c0000h?2c7fffh 96 64/32 590000h?59ffffh 2c8000h?2cffffh 97 64/32 5a0000h?5affffh 2d0000h?2d7fffh 98 64/32 5b0000h?5bffffh 2d8000h?2dffffh 99 64/32 protection group 5c0000h?5cffffh 2e0000h?2e7fffh 100 64/32 5d0000h?5dffffh 2e8000h?2effffh 101 64/32 5e0000h?5effffh 2f0000h?2f7fffh 102 64/32 5f0000h?5fffffh 2f8000h?2fffffh 103 64/32 protection group 600000h?60ffffh 300000h?307fffh 104 64/32 610000h?61ffffh 308000h?30ffffh 105 64/32 620000h?62ffffh 310000h?317fffh 106 64/32 630000h?63ffffh 318000h?31ffffh 107 64/32 protection group 640000h?64ffffh 320000h?327fffh 108 64/32 650000h?65ffffh 328000h?32ffffh 109 64/32 660000h?66ffffh 330000h?337fffh 110 64/32 670000h?67ffffh 338000h?33ffffh 111 64/32 protection group 680000h?68ffffh 340000h?347fffh 112 64/32 690000h?69ffffh 348000h?34ffffh 113 64/32 6a0000h?6affffh 350000h?357fffh 114 64/32 6b0000h?6bffffh 358000h?35ffffh 115 64/32 protection group 6c0000h?6cffffh 360000h?367fffh 116 64/32 6d0000h?6dffffh 368000h?36ffffh 117 64/32 6e0000h?6effffh 370000h?377fffh 118 64/32 6f0000h?6fffffh 378000h?37ffffh 119 64/32 protection group 700000h?70ffffh 380000h?387fffh 120 64/32 710000h?71ffffh 388000h?38ffffh 121 64/32 720000h?72ffffh 390000h?397fffh 122 64/32 730000h?73ffffh 398000h?39ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
m29dw128f 12 part numbering 71/93 bank b 123 64/32 protection group 740000h?74ffffh 3a0000h?3a7fffh 124 64/32 750000h?75ffffh 3a8000h?3affffh 125 64/32 760000h?76ffffh 3b0000h?3b7fffh 126 64/32 770000h?77ffffh 3b8000h?3bffffh 127 64/32 protection group 780000h?78ffffh 3c0000h?3c7fffh 128 64/32 790000h?79ffffh 3c8000h?3cffffh 129 64/32 7a0000h?7affffh 3d0000h?3d7fffh 130 64/32 7b0000h?7bffffh 3d8000h?3dffffh 131 64/32 protection group 7c0000h?7cffffh 3e0000h?3e7fffh 132 64/32 7d0000h?7dffffh 3e8000h?3effffh 133 64/32 7e0000h?7effffh 3f0000h?3f7fffh 134 64/32 7f0000h-7fffffh 3f8000h-3fffffh bank c 135 64/32 protection group 800000h?80ffffh 400000h?407fffh 136 64/32 810000h?81ffffh 408000h?40ffffh 137 64/32 820000h?82ffffh 410000h?417fffh 138 64/32 830000h?83ffffh 418000h?41ffffh 139 64/32 protection group 840000h?84ffffh 420000h?427fffh 140 64/32 850000h?85ffffh 428000h?42ffffh 141 64/32 860000h?86ffffh 430000h?437fffh 142 64/32 870000h?87ffffh 438000h?43ffffh 143 64/32 protection group 880000h?88ffffh 440000h?447fffh 144 64/32 890000h?89ffffh 448000h?44ffffh 145 64/32 8a0000h?8affffh 450000h?457fffh 146 64/32 8b0000h?8bffffh 458000h?45ffffh 147 64/32 protection group 8c0000h?8cffffh 460000h?467fffh 148 64/32 8d0000h?8dffffh 468000h?46ffffh 149 64/32 8e0000h?8effffh 470000h?477fffh 150 64/32 8f0000h-8fffffh 478000h?47ffffh 151 64/32 protection group 900000h-90ffffh 480000h?487fffh 152 64/32 910000h?91ffffh 488000h?48ffffh 153 64/32 920000h?92ffffh 490000h?497fffh 154 64/32 930000h?93ffffh 498000h?49ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
12 part numbering m29dw128f 72/93 bank c 155 64/32 protection group 940000h?94ffffh 4a0000h?4a7fffh 156 64/32 950000h?95ffffh 4a8000h?4affffh 157 64/32 960000h?96ffffh 4b0000h?4b7fffh 158 64/32 970000h?97ffffh 4b8000h?4bffffh 159 64/32 protection group 980000h?98ffffh 4c0000h?4c7fffh 160 64/32 990000h?99ffffh 4c8000h?4cffffh 161 64/32 9a0000h?9affffh 4d0000h?4d7fffh 162 64/32 9b0000h?9bffffh 4d8000h?4dffffh 163 64/32 protection group 9c0000h?9cffffh 4e0000h?4e7fffh 164 64/32 9d0000h?9dffffh 4e8000h?4effffh 165 64/32 9e0000h?9effffh 4f0000h?4f7fffh 166 64/32 9f0000h?9fffffh 4f8000h-4fffffh 167 64/32 protection group a00000h?a0ffffh 500000h?507fffh 168 64/32 a10000h?a1ffffh 508000h?50ffffh 169 64/32 a20000h?a2ffffh 510000h?517fffh 170 64/32 a30000h?a3ffffh 518000h?51ffffh 171 64/32 protection group a40000h?a4ffffh 520000h?527fffh 172 64/32 a50000h?a5ffffh 528000h?52ffffh 173 64/32 a60000h?a6ffffh 530000h?537fffh 174 64/32 a70000h?a7ffffh 538000h?53ffffh 175 64/32 protection group a80000h?a8ffffh 540000h?547fffh 176 64/32 a90000h?a9ffffh 548000h?54ffffh 177 64/32 aa0000h?aaffffh 550000h?557fffh 178 64/32 ab0000h?abffffh 558000h?55ffffh 179 64/32 protection group ac0000h?acffffh 560000h?567fffh 180 64/32 ad0000h?adffffh 568000h?56ffffh 181 64/32 ae0000h?aeffffh 570000h?577fffh 182 64/32 af0000h-afffffh 578000h?57ffffh 183 64/32 protection group b00000h?b0ffffh 580000h?587fffh 184 64/32 b10000h?b1ffffh 588000h?58ffffh 185 64/32 b20000h?b2ffffh 590000h?597fffh 186 64/32 b30000h-b3ffffh 598000h?59ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
m29dw128f 12 part numbering 73/93 bank c 187 64/32 protection group b40000h?b4ffffh 5a0000h?5a7fffh 188 64/32 b50000h?b5ffffh 5a8000h?5affffh 189 64/32 b60000h?b6ffffh 5b0000h?5b7fffh 190 64/32 b70000h-b7ffffh 5b8000h?5bffffh 191 64/32 protection group b80000h?b8ffffh 5c0000h?5c7fffh 192 64/32 b90000h?b9ffffh 5c8000h?5cffffh 193 64/32 ba0000h?baffffh 5d0000h?5d7fffh 194 64/32 bb0000h?bbffffh 5d8000h?5dffffh 195 64/32 protection group bc0000h?bcffffh 5e0000h?5e7fffh 196 64/32 bd0000h?bdffffh 5e8000h?5effffh 197 64/32 be0000h?beffffh 5f0000h?5f7fffh 198 64/32 bf0000h?bfffffh 5f8000h-5fffffh 199 64/32 protection group c00000h?c0ffffh 600000h?607fffh 200 64/32 c10000h?c1ffffh 608000h?60ffffh 201 64/32 c20000h?c2ffffh 610000h?617fffh 202 64/32 c30000h?c3ffffh 618000h?61ffffh 203 64/32 protection group c40000h?c4ffffh 620000h?627fffh 204 64/32 c50000h?c5ffffh 628000h?62ffffh 205 64/32 c60000h?c6ffffh 630000h?637fffh 206 64/32 c70000h-c7ffffh 638000h?63ffffh 207 64/32 protection group c80000h?c8ffffh 640000h?647fffh 208 64/32 c90000h?c9ffffh 648000h?64ffffh 209 64/32 ca0000h?caffffh 650000h?657fffh 210 64/32 cb0000h?cbffffh 658000h?65ffffh 211 64/32 protection group cc0000h?ccffffh 660000h?667fffh 212 64/32 cd0000h?cdffffh 668000h?66ffffh 213 64/32 ce0000h?ceffffh 670000h?677fffh 214 64/32 cf0000h-cfffffh 678000h?67ffffh 215 64/32 protection group d00000h?d0ffffh 680000h?687fffh 216 64/32 d10000h?d1ffffh 688000h?68ffffh 217 64/32 d20000h?d2ffffh 690000h?697fffh 218 64/32 d30000h?d3ffffh 698000h?69ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
12 part numbering m29dw128f 74/93 bank c 219 64/32 protection group d40000h?d4ffffh 6a0000h?6a7fffh 220 64/32 d50000h?d5ffffh 6a8000h?6affffh 221 64/32 d60000h?d6ffffh 6b0000h?6b7fffh 222 64/32 d70000h-d7ffffh 6b8000h?6bffffh 223 64/32 protection group d80000h-d8ffffh 6c0000h?6c7fffh 224 64/32 d90000h-d9ffffh 6c8000h?6cffffh 225 64/32 da0000h-daffffh 6d0000h?6d7fffh 226 64/32 db0000h-dbffffh 6d8000h?6dffffh 227 64/32 protection group dc0000h-dcffffh 6e0000h?6e7fffh 228 64/32 dd0000h-ddffffh 6e8000h?6effffh 229 64/32 de0000h-deffffh 6f0000h?6f7fffh 230 64/32 df0000h-dfffffh 6f8000h-6fffffh bank d 231 64/32 protection group e00000h-e0ffffh 700000h?707fffh 232 64/32 e10000h-e1ffffh 708000h?70ffffh 233 64/32 e20000h-e2ffffh 710000h?717fffh 234 64/32 e30000h-e3ffffh 718000h?71ffffh 235 64/32 protection group e40000h-e4ffffh 720000h?727fffh 236 64/32 e50000h-e5ffffh 728000h?72ffffh 237 64/32 e60000h-e6ffffh 730000h?737fffh 238 64/32 e70000h-e7ffffh 738000h?73ffffh 239 64/32 protection group e80000h-e8ffffh 740000h?747fffh 240 64/32 e90000h-e9ffffh 748000h?74ffffh 241 64/32 ea0000h-eaffffh 750000h?757fffh 242 64/32 eb0000h-ebffffh 758000h?75ffffh 243 64/32 protection group ec0000h-ecffffh 760000h?767fffh 244 64/32 ed0000h-edffffh 768000h?76ffffh 245 64/32 ee0000h-eeffffh 770000h?777fffh 246 64/32 ef0000h-efffffh 778000h?77ffffh 247 64/32 protection group f00000h-f0ffffh 780000h?787fffh 248 64/32 f10000h-f1ffffh 788000h?78ffffh 249 64/32 f20000h-f2ffffh 790000h?797fffh 250 64/32 f30000h-f3ffffh 798000h?79ffffh bank block size (kbytes/ kwords) protection block group (x8) (x16)
m29dw128f 12 part numbering 75/93 bank d 251 64/32 protection group f40000h-f4ffffh 7a0000h?7a7fffh 252 64/32 f50000h-f5ffffh 7a8000h?7affffh 253 64/32 f60000h-f6ffffh 7b0000h?7b7fffh 254 64/32 f70000h-f7ffffh 7b8000h?7bffffh 255 64/32 protection group f80000h-f8ffffh 7c0000h?7c7fffh 256 64/32 f90000h-f9ffffh 7c8000h?7cffffh 257 64/32 fa0000h-faffffh 7d0000h?7d7fffh 258 64/32 fb0000h-fbffffh 7d8000h?7dffffh 259 64/32 protection group fc0000h-fcffffh 7e0000h?7e7fffh 260 64/32 fd0000h-fdffffh 7e8000h?7effffh 261 64/32 fe0000h-feffffh 7f0000h-7f7fffh 262 8/4 protection group ff0000h-ff1fffh (1) 7f8000h-7f8fffh (1) 263 8/4 protection group ff2000h-ff3fffh (1) 7f9000h-7f9fffh (1) 264 8/4 protection group ff4000h-ff5fffh (1) 7fa000h-7fafffh (1) 265 8/4 protection group ff6000h-ff7fffh (1) 7fb000h-7fbfffh (1) 266 8/4 protection group ff8000h-ff9fffh (1) 7fc000h-7fcfffh (1) 267 8/4 protection group ffa000h-ffbfffh (1) 7fd000h-7fdfffh (1) 268 8/4 protection group ffc000h-ffdfffh (1) 7fe000h-7fefffh (1) 269 8/4 protection group ffe000h-ffffffh (1) 7ff000h-7fffffh (1) 1. parameter blocks. bank block size (kbytes/ kwords) protection block group (x8) (x16)
12 part numbering m29dw128f 76/93 appendix b common flash interface (cfi) the common flash interface is a jedec approved, standardized data structure that can be read from the flash memory device. it allows a system software to query the device to determine various electrical and timing parameters, density information and functions supported by the memory. the system can interface easily with the device, enabling the software to upgrade itself when necessary. when the read cfi query command is issued the addressed bank enters read cfi query mode and read operations in the same bank (a22-a19) output the cfi data. ta bl e 3 5 , ta b l e 3 6 , ta b l e 3 7 , ta b l e 3 8 , ta bl e 3 9 and ta b l e 4 0 show the addresses (a-1, a0-a10) used to retrieve the data. the cfi data structure also contains a security area where a 64 bit unique security number is written (see table 40: security code area ). this area can be accessed only in read mode by the final user. it is impossible to change the security number after it has been written by st. table 35. query structure overview 1. query data are always presented on the lowest order data outputs. address sub-section name description x16 x8 10h 20h cfi query identification string command set id and algorithm data offset 1bh 36h system interface information device timing & voltage information 27h 4eh device geometry definition flash device layout 40h 80h primary algorithm-specific extended query table additional information specific to the primary algorithm (optional) 61h c2h security code area 64 bit unique device number
m29dw128f 12 part numbering 77/93 table 36. cfi query identification string 1. query data are always presented on the lowest order data outputs (dq7-dq0) only. dq8-dq15 are ?0?. address data description value x16 x8 10h 20h 0051h ?q? 11h 22h 0052h query unique ascii string "qry" "r" 12h 24h 0059h "y" 13h 26h 0002h primary algorithm command set and control interface id code 16 bit id code defining a specific algorithm amd compatible 14h 28h 0000h 15h 2ah 0040h address for primary algorithm extended query table (see ta bl e 3 9 )p = 40h 16h 2ch 0000h 17h 2eh 0000h alternate vendor command set and control interface id code second vendor - specified algorithm supported na 18h 30h 0000h 19h 32h 0000h address for alternate algorithm extended query table na 1ah 34h 0000h
12 part numbering m29dw128f 78/93 table 37. cfi query system interface information 1. the values given in the above table are valid for both packages. address data description value x16 x8 1bh 36h 0027h v cc logic supply minimum program/erase voltage bit 7 to 4bcd value in volts bit 3 to 0bcd value in 100mv 2.7v 1ch 38h 0036h v cc logic supply maximum program/erase voltage bit 7 to 4bcd value in volts bit 3 to 0bcd value in 100mv 3.6v 1dh 3ah 00b5h v pp [programming] supply minimum program/erase voltage bit 7 to 4hex value in volts bit 3 to 0bcd value in 100mv 11.5v 1eh 3ch 00c5h v pp [programming] supply maximum program/erase voltage bit 7 to 4hex value in volts bit 3 to 0bcd value in 10mv 12.5v 1fh 3eh 0004h typical timeout per single byte/word program = 2 n s 16s 20h 40h 0000h typical timeout for minimum size write buffer program = 2 n s na 21h 42h 0009h typical timeout per individual block erase = 2 n ms 512ms 22h 44h 0000h typical timeout for full chip erase = 2 n ms na 23h 46h 0005h maximum timeout for byte/word program = 2 n times typical 512s 24h 48h 0000h maximum timeout for write buffer program = 2 n times typical na 25h 4ah 0004h maximum timeout per individual block erase = 2 n times typical 8s 26h 4ch 0000h maximum timeout for chip erase = 2 n times typical na
m29dw128f 12 part numbering 79/93 table 38. device geometry definition 1. erase block region 1 corresponds to addresses 000000h to 007fffh; erase block region 2 corresponds to addresses 008000h to 3f7fffh and erase block region 3 corresponds to addresses 3f8000h to 3fffffh. address data description value x16 x8 27h 4eh 0018h device size = 2 n in number of bytes 16 mbytes 28h 50h 0001h tbga64 (x16 only) flash device interface code description x8, x16 async. 0002h tsop56 (x8/x16) 29h 52h 0000h both packages 2ah 54h 0006h maximum number of bytes in multiple-byte program or page= 2 n 64 2bh 56h 0000h 2ch 58h 0003h number of erase block regions (1) . it specifies the number of regions containing contiguous erase blocks of the same size. 3 2dh 2eh 5ah 5ch 0007h 0000h erase block region 1 information number of erase blocks of identical size = 0007h+1 8 2fh 30h 5eh 60h 0020h 0000h erase block region 1 information block size in region 1 = 0020h * 256 byte 8 kbytes 31h 32h 62h 64h 00fdh 0000h erase block region 2 information number of erase blocks of identical size = 00fdh+1 254 33h 34h 66h 68h 0000h 0001h erase block region 2 information block size in region 2 = 0100h * 256 byte 64 kbytes 35h 36h 6ah 6ch 0007h 0000h erase block region 3 information number of erase blocks of identical size = 0007h + 1 8 37h 38h 6eh 70h 0020h 0000h erase block region 3 information block size in region 3 = 0020h * 256 bytes 8 kbytes 39h 3ah 3bh 3ch 72h 74h 76h 78h 0000h 0000h 0000h 0000h erase block region 4 information 0
12 part numbering m29dw128f 80/93 table 39. primary algorithm-specific extended query table address data description value x16 x8 40h 80h 0050h primary algorithm extended query table unique ascii string ?pri? "p" 41h 82h 0052h "r" 42h 84h 0049h "i" 43h 86h 0031h major version number, ascii "1" 44h 88h 0033h minor version number, ascii "3" 45h 8ah 000ch address sensitive unlock (bits 1 to 0) 00 = required, 01= not required silicon revision number (bits 7 to 2) ye s 46h 8ch 0002h erase suspend 00 = not supported, 01 = read only, 02 = read and write 2 47h 8eh 0001h block protection 00 = not supported, x = number of sectors in per group 1 48h 90h 0001h temporary block unprotect 00 = not supported, 01 = supported ye s 49h 92h 0006h block protect /unprotect 06 = m29dw128f 6 4ah 94h 00e7 simultaneous operations, x = number of blocks (excluding bank a) 231 4bh 96h 0000h burst mode, 00 = not supported, 01 = supported no 4ch 98h 0002h page mode, 00 = not supported, 02 = 8-word page yes 4dh 9ah 00b5h v pp supply minimum program/erase voltage bit 7 to 4 hex value in volts bit 3 to 0 bcd value in 100mv 11.5v 4eh 9ch 00c5h v pp supply maximum program/erase voltage bit 7 to 4 hex value in volts bit 3 to 0 bcd value in 100mv 12.5v 4fh 9eh 0001h top/bottom boot block flag 00h = uniform device 01h = 8 x8 kbyte blocks or 4kwords, top and bottom boot with write protect 02h = bottom boot device 03h = top boot device 04h = both top and bottom t/b 50h a0h 0001h program suspend, 00 = not supported, 01 = supported yes 57h aeh 0004h bank organization, 00 = data at 4ah is zero x = number of banks 4 58h b0h 0027h bank a information x = number of blocks in bank a 39
m29dw128f 12 part numbering 81/93 1. the values given in the above table are valid for both packages. table 40. security code area 59h b2h 0060h bank b information x = number of blocks in bank b 96 5ah b4h 0060h bank c information x = number of blocks in bank c 96 5bh b6h 0027h bank d information x = number of blocks in bank d 39 address data description x16 x8 61h c3h, c2h xxxx 64 bit: unique device number 62h c5h, c4h xxxx 63h c7h, c6h xxxx 64h c9h, c8h xxxx address data description value x16 x8
12 part numbering m29dw128f 82/93 appendix c extended memory block the m29dw128f has an extra block, the extended block, that can be accessed using a dedicated command. this extended block is 128 words in x16 mode and 256 bytes in x8 mode. it is used as a security block (to provide a permanent security identification number) or to store additional information. the extended block is divided into two memory areas of 64 words each: the first one is factory locked. the second one is customer lockable. it is up to the customer to protect it from program operations. its status is indicated by bit dq6 and dq7. when dq7 is set to ?1? and dq6 to ?0?, it indicates that this second memory area is customer lockable. when dq7 and dq6 are both set to ?1?, it indicates that the second part of the extended block is customer locked and protected from program operations. bit dq7 being permanently locked to either ?1? or ?0? is another security feature which ensures that a customer lockable device cannot be used instead of a factory locked one. bits dq6 and dq7 are the most significant bits in the extended block protection indicator and a specific procedure must be followed to read it. see ? section 3.6.2: verify extended block protection indicator ? and ta b l e 5 and ta b l e 8 , block protection, for details of how to read bit dq7. the extended block can only be accessed when the device is in extended block mode. for details of how the extended block mode is entered and exited, refer to the program command and exit extended block command paragraphs, and to ta b l e 1 5 and ta b l e 1 6 , block protection commands. c.1 factory locked section of the extended block the first section of the extended block is permanently protected from program operations and cannot be unprotected. the random number, electronic serial number (esn) and security identification number (see table 41: extended block address and data ) are written in this section in the factory. c.2 customer lockable section of the extended block the device is delivered with the second section of the extended block "customer lockable": bits dq7 and dq6 are set to '1' and '0' respectively. it is up to the customer to program and protect this section of the extended block but care must be taken because the protection is not reversible. there are three ways of protecting this section: issue the enter extended block command to place the device in extended block mode, then use the in-system technique with rp either at v ih or at v id . refer to in-system technique in appendix d: high voltage block protection , and to the corresponding flowcharts figure 25 and figure 26 for a detailed explanation of the technique). issue the enter extended block command to place the device in extended block mode, then use the programmer technique. refer to programmer technique in appendix d: high
m29dw128f 12 part numbering 83/93 voltage block protection , and to the corresponding flowcharts figure 23 and figure 24 for a detailed explanation of the technique). issue a set extended block protection bit command to program the extended block protection bit to ?1? thus preventing the second section of the extended block from being programmed. bit dq6 of the extended block protection indicator is automatically set to '1' to indicate that the second section of the extended block is customer locked. once the extended block is programmed and protected, the exit extended block command must be issued to exit the extended block mode and return the device to read mode. table 41. extended block address and data device address (1) 1. see table 34: block addresses and protection groups . data x8 x16 factory locked customer lockable m29dw128f 000000h- 00007fh 000000h- 00003fh random number, esn (2) , security identification number 2. esn = electronic serial number. unavailable 000080h- 0000ffh 000040h- 00007fh unavailable determined by customer
12 part numbering m29dw128f 84/93 appendix d high voltage block protection the high voltage block protection can be used to prevent any operation from modifying the data stored in the memory. the blocks are protected in groups, refer to appendix a , ta b l e 3 4 for details of the protection groups. once protected, program and erase operations within the protected group fail to change the data. there are three techniques that can be used to control block protection, these are the programmer technique, the in-system technique and temporary unprotection. temporary unprotection is controlled by the reset/block temporary unprotection pin, rp ; this is described in the signal descriptions section. to protect the extended block issue the enter extended block command and then use either the programmer or in-system technique. once protected issue the exit extended block command to return to read mode. the extended block protection is irreversible, once protected the protection cannot be undone. d.1 programmer technique the programmer technique uses high (v id ) voltage levels on some of the bus pins. these cannot be achieved using a standard microprocessor bus, therefore the technique is recommended only for use in programming equipment. to protect a group of blocks follow the flowchart in figure 23: programmer equipment group protect flowchart . to unprotect the whole chip it is necessary to protect all of the groups first, then all groups can be unprotected at the same time. to unprotect the chip follow figure 24: programmer equipment chip unprotect flowchart . table 42: programmer technique bus operations, 8-bit or 16-bit mode , gives a summary of each operation. the timing on these flowcharts is critical. care should be taken to ensure that, where a pause is specified, it is followed as closely as possible. do not abort the procedure before reaching the end. chip unprotect can take several seconds and a user message should be provided to show that the operation is progressing. d.2 in-system technique the in-system technique requires a high voltage level on the reset/blocks temporary unprotect pin, rp (1) . this can be achieved without violating the maximum ratings of the components on the microprocessor bus, therefore this technique is suitable for use after the memory has been fitted to the system. to protect a group of blocks follow the flowchart in figure 25: in-system equipment group protect flowchart . to unprotect the whole chip it is necessary to protect all of the groups first, then all the groups can be unprotected at the same time. to unprotect the chip follow figure 26: in-system equipment chip unprotect flowchart . the timing on these flowcharts is critical. care should be taken to ensure that, where a pause is specified, it is followed as closely as possible. do not allow the microprocessor to service interrupts that will upset the timing and do not abort the procedure before reaching the end. chip unprotect can take several seconds and a user message should be provided to show that the operation is progressing.
m29dw128f 12 part numbering 85/93 note 1: rp can be either at v ih or at v id when using the in-system technique to protect the extended block. table 42. programmer technique bus operations, 8-bit or 16-bit mode operation e g w address inputs a0-a22 data inputs/outputs dq15a?1, dq14-dq0 block (group) protect (1) 1. block protection groups are shown in appendix d , table 34 . v il v id v il pulse a9 = v id , a12-a22 block address others = x x chip unprotect v id v id v il pulse a6 = v ih , a9 = v id , a12 = v ih , a15 = v ih others = x x block (group) protect verify v il v il v ih a0 = v il , a1 = v ih , a2-a7 = v il , a9 = v id , a12-a22 block address others = x pass = xx01h retry = xx00h. block (group) unprotect verify v il v il v ih a0 = v il , a1 = v ih , a2 -a5 = v il , a6 = v ih , a7 = v il , a9 = v id , a12-a22 block address others = x pass = xx00h retry = xx01h.
12 part numbering m29dw128f 86/93 appendix e flowcharts figure 23. programmer equipment group protect flowchart 1. block protection groups are shown in appendix d , table 34 . address = group address ai07756b g, a9 = v id , e = v il n = 0 wait 4s wait 100s w = v il w = v ih e, g = v ih , a1 = v ih a0, a2 to a7 = v il a9 = v ih e, g = v ih ++n = 25 start fail pass yes no data = 01h yes no w = v ih e = v il wait 4s g = v il wait 60ns read data verify protect set-up end a9 = v ih e, g = v ih
m29dw128f 12 part numbering 87/93 figure 24. programmer equipment chip unprotect flowchart 1. block protection groups are shown in appendix d , table 34 . protect all groups ai07757b a6, a12, a15 = v ih (1) e, g, a9 = v id data = 00h w = v ih e, g = v ih address = current group address a0, a2, a3, a4, a5, a7 = v il a1, a6 = v ih wait 10ms increment current group n = 0 current group = 0 wait 4s w = v il ++n = 1000 start yes yes no no last group yes no e = v il wait 4s g = v il wait 60ns read data fail pass verify unprotect set-up end a9 = v ih e, g = v ih a9 = v ih e, g = v ih
12 part numbering m29dw128f 88/93 figure 25. in-system equipment group protect flowchart 1. block protection groups are shown in appendix d , table 34 . 2. rp can be either at v ih or at v id when using the in-system technique to protect the extended block. ai07758b write 60h address = group address a0, a2, a3, a6 = v il, a1 = v ih n = 0 wait 100s write 40h address = group address a0, a2, a3, a6 = v il, a1 = v ih rp = v ih ++n = 25 start pass yes no data = 01h yes no rp = v ih wait 4s verify protect set-up end read data address = group address a1 = v ih , a0, a2 to a7 = v il rp = v id issue read/reset command write 60h address = group address a0, a2, a3, a6 = v il, a1 = v ih issue read/reset command fail
m29dw128f 12 part numbering 89/93 figure 26. in-system equipment chip unprotect flowchart 1. block protection groups are shown in appendix d , table 34 . ai07759d write 60h any address with a0, a2, a3, a4, a5, a7 = v il a1, a6 = v ih n = 0 current group = 0 wait 10ms write 40h address = current group address a1 = v ih , a0, a2 to a7 = v il rp = v ih ++n = 1000 start fail pass no data = 00h yes no rp = v ih wait 4s read data address = current group address a1 = v ih , a0, a2 to a7 = v il rp = v id issue read/reset command issue read/reset command protect all groups increment current group last group yes no write 60h any address with a1 = v ih , a0, a2 to a7 = v il verify unprotect set-up end yes
12 part numbering m29dw128f 90/93 figure 27. write to buffer and program flowchart and pseudo code 1. n+1 is the number of addresses to be programmed. 2. a write to buffer and program abort and reset mu st be issued to return the device in read mode. write to buffer f0h command, block address ai08968b start write buffer data, start address yes abort write to buffer fail or abort (5) no write n (1) , block address x = 0 write next data, program address pair x = x-1 program buffer to flash block address read status register (dq1, dq5, dq7) at last loaded address yes dq7 = data no check status register (dq5, dq7) at last loaded address (3) no yes write to a different block address write to buffer and program aborted (2) no dq5 = 1 yes no dq1 = 1 yes yes dq7 = data (4) no end first part of the write to buffer and program command x=n
m29dw128f 12 part numbering 91/93 3. when the block address is specified, any address in the selected block addres s space is acceptable. however when loading write buffer address with data, all addresses must fall within the selected write buffer page. 4. dq7 must be checked since dq5 and dq7 may change simultaneously. 5. if this flowchart location is reached because dq5=?1?, then the write to buffer and program command failed. if this flowchart location is reached because dq1=?1?, then the write to buffer and program command aborted. in both cases, the appropriate reset command must be issued to return the device in read mode: a reset command if the operation failed, a write to buffer and program abort and reset command if the operation aborted. 6. see table 11 and table 12 , for details on write to buffer and program command sequence.
13 revision history m29dw128f 92/93 13 revision history table 43. document revision history date version revision details 02-aug-2005 0.1 first issue derived from the m29dw128f/fs datasheet revision 0.5.
m29dw128f 93/93 information furnished is believed to be accurate and reliable. however, stmicroelectronics assu mes no responsibility for the co nsequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications mentioned in this publicati on are subject to change without notice. this publication supersedes and replaces all information previously supplied. stmicroelectronics prod ucts are not authorized for use as critical components in life support devices or systems without express written approval of stmicroelectro nics. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners ? 2005 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of M29DW128F70ZA6

	To Download M29DW128F70ZA6 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .